BUG: unable to handle kernel paging request in kvm_arch_vcpu_ioctl_run

[syzbot]

Hello,

syzkaller hit the following crash on
d5c52866f560ba43edcb941868e1f884f15234e5
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.

Unfortunately, I don't have any reproducer for this bug yet.
CC: [h...@zytor.com k...@vger.kernel.org linux-...@vger.kernel.org
mi...@redhat.com pbon...@redhat.com rkr...@redhat.com tg...@linutronix.de
x...@kernel.org]

BUG: unable to handle kernel paging request at 00000000e5a31341
IP: srcu_read_unlock include/linux/srcu.h:175 [inline]
IP: vcpu_enter_guest arch/x86/kvm/x86.c:6967 [inline]
IP: vcpu_run arch/x86/kvm/x86.c:7146 [inline]
IP: kvm_arch_vcpu_ioctl_run+0xd9d/0x5c60 arch/x86/kvm/x86.c:7314
PGD 5e28067 P4D 5e28067 PUD 5e2a067 PMD 0
Oops: 0002 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 7763 Comm: *q/wlan1 Not tainted 4.15.0-rc2-next-20171206+ #60
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:srcu_read_unlock include/linux/srcu.h:175 [inline]
RIP: 0010:vcpu_enter_guest arch/x86/kvm/x86.c:6967 [inline]
RIP: 0010:vcpu_run arch/x86/kvm/x86.c:7146 [inline]
RIP: 0010:kvm_arch_vcpu_ioctl_run+0xd9d/0x5c60 arch/x86/kvm/x86.c:7314
RSP: 0018:ffff8801bfc2f6b0 EFLAGS: 00010082
RAX: 000060fe248339c0 RBX: ffff88018e52aa78 RCX: ffff8801d845eae8
RDX: 1ffff10031ca55e2 RSI: 0000000000000000 RDI: ffff88018e52af10
RBP: ffff8801bfc2fa40 R08: ffff88018e52b118 R09: 1ffff10037f85eaf
R10: ffff8801d845e200 R11: 0000000000000001 R12: 0000000000000000
R13: dffffc0000000000 R14: ffff8801c0d38870 R15: ffff8801c0d38840
FS: 00007f0486d1f700(0000) GS:ffff8801db500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff8 CR3: 00000001c8ad5000 CR4: 00000000001426e0
DR0: 0000000000000001 DR1: 0000000000000007 DR2: 0000000000000009
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
kvm_vcpu_ioctl+0x64c/0x1010 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2555
vfs_ioctl fs/ioctl.c:46 [inline]
do_vfs_ioctl+0x1b1/0x1530 fs/ioctl.c:686
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x8f/0xc0 fs/ioctl.c:692
entry_SYSCALL_64_fastpath+0x1f/0x96
RIP: 0033:0x452a39
RSP: 002b:00007f0486d1ec58 EFLAGS: 00000212 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000758020 RCX: 0000000000452a39
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000015
RBP: 0000000000000164 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000212 R12: 00000000006ef200
R13: 00000000ffffffff R14: 00007f0486d1f6d4 R15: 0000000000000000
Code: fc ff ff e8 e6 44 62 00 48 8b bd e8 fc ff ff 48 c7 c2 3d f7 0d 81 be
01 00 00 00 e8 ce 60 48 00 44 89 e6 48 89 df e8 23 9d 4e 00 <cc> fe 16 00
00 e8 b9 44 62 00 49 8d bf e0 03 00 00 48 89 f8 48
RIP: srcu_read_unlock include/linux/srcu.h:175 [inline] RSP:
ffff8801bfc2f6b0
RIP: vcpu_enter_guest arch/x86/kvm/x86.c:6967 [inline] RSP: ffff8801bfc2f6b0
RIP: vcpu_run arch/x86/kvm/x86.c:7146 [inline] RSP: ffff8801bfc2f6b0
RIP: kvm_arch_vcpu_ioctl_run+0xd9d/0x5c60 arch/x86/kvm/x86.c:7314 RSP:
ffff8801bfc2f6b0
CR2: fffffffffffffff8
---[ end trace 93d8dcad9156a359 ]---
Kernel panic - not syncing: Fatal exception
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
Please credit me with: Reported-by: syzbot <syzk...@googlegroups.com>

syzbot will keep track of this bug report.
Once a fix for this bug is merged into any tree, reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
To upstream this report, please reply with:
#syz upstream

[Dmitry Vyukov]

#syz fix:
x86/entry: Fix assumptions that the HW TSS is at the beginning of cpu_tss


On Sun, Dec 10, 2017 at 9:26 PM, syzbot
<bot+f9964696181d44c0e2...@syzkaller.appspotmail.com>
wrote:

> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To post to this group, send email to
> syzkaller-upst...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/001a1144d1c8f88ac505600239ea%40google.com.
> For more options, visit https://groups.google.com/d/optout.