invalid opcode in __phys_addr

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 459e3a21 gcc-9: properly declare the {pv,hv}clock_page sto..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15ff0148a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=ef1b87b455c397cf
dashboard link: https://syzkaller.appspot.com/bug?extid=e8e5d8567dd2cb6098fb
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
CC: [ax...@kernel.dk linux...@vger.kernel.org
linux-...@vger.kernel.org linux-...@vger.kernel.org
vi...@zeniv.linux.org.uk]

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+e8e5d8...@syzkaller.appspotmail.com

invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 26533 Comm: syz-executor.1 Not tainted 5.1.0-rc7+ #95
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__phys_addr+0xb3/0x120 arch/x86/mm/physaddr.c:27
Code: 08 4c 89 e3 31 ff 48 d3 eb 48 89 de e8 16 c3 3d 00 48 85 db 75 0f e8
6c c1 3d 00 4c 89 e0 5b 41 5c 41 5d 5d c3 e8 5d c1 3d 00 <0f> 0b e8 56 c1
3d 00 48 c7 c0 10 90 87 88 48 ba 00 00 00 00 00 fc
RSP: 0018:ffff888053517d48 EFLAGS: 00010216
RAX: 0000000000040000 RBX: 0000000000000000 RCX: ffffc90008070000
RDX: 000000000000847c RSI: ffffffff8132cb53 RDI: 0000000000000006
RBP: ffff888053517d60 R08: ffff888087a9a380 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000778000000000
R13: 0000000080000000 R14: ffff8880a0ff8b80 R15: fffffffffffffff4
FS: 00007fd5b8e2a700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcadf176000 CR3: 00000000973e6000 CR4: 00000000001406f0
DR0: 000000000000b8c4 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
virt_to_head_page include/linux/mm.h:686 [inline]
io_mem_free+0x23/0x150 fs/io_uring.c:2324
io_ring_ctx_free fs/io_uring.c:2558 [inline]
io_ring_ctx_wait_and_kill+0x290/0x510 fs/io_uring.c:2603
io_uring_create fs/io_uring.c:2890 [inline]
io_uring_setup+0x1305/0x1ac0 fs/io_uring.c:2916
__do_sys_io_uring_setup fs/io_uring.c:2929 [inline]
__se_sys_io_uring_setup fs/io_uring.c:2926 [inline]
__x64_sys_io_uring_setup+0x54/0x80 fs/io_uring.c:2926
do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x458da9
Code: ad b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 7b b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fd5b8e29c78 EFLAGS: 00000246 ORIG_RAX: 00000000000001a9
RAX: ffffffffffffffda RBX: 00007fd5b8e29c90 RCX: 0000000000458da9
RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000727
RBP: 000000000073bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fd5b8e2a6d4
R13: 00000000004bffde R14: 00000000004d2318 R15: 0000000000000004
Modules linked in:
---[ end trace 8d6c64af213fe7db ]---
RIP: 0010:__phys_addr+0xb3/0x120 arch/x86/mm/physaddr.c:27
Code: 08 4c 89 e3 31 ff 48 d3 eb 48 89 de e8 16 c3 3d 00 48 85 db 75 0f e8
6c c1 3d 00 4c 89 e0 5b 41 5c 41 5d 5d c3 e8 5d c1 3d 00 <0f> 0b e8 56 c1
3d 00 48 c7 c0 10 90 87 88 48 ba 00 00 00 00 00 fc
RSP: 0018:ffff888053517d48 EFLAGS: 00010216
RAX: 0000000000040000 RBX: 0000000000000000 RCX: ffffc90008070000
RDX: 000000000000847c RSI: ffffffff8132cb53 RDI: 0000000000000006
RBP: ffff888053517d60 R08: ffff888087a9a380 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000778000000000
R13: 0000000080000000 R14: ffff8880a0ff8b80 R15: fffffffffffffff4
FS: 00007fd5b8e2a700(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000001e750d8 CR3: 00000000973e6000 CR4: 00000000001406e0
DR0: 000000000000b8c4 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.