WARNING in handle_ept_misconfig

13 views
Skip to first unread message

syzbot

unread,
Oct 26, 2017, 12:35:21 PM10/26/17
to h...@zytor.com, k...@vger.kernel.org, linux-...@vger.kernel.org, mi...@redhat.com, pbon...@redhat.com, rkr...@redhat.com, syzkall...@googlegroups.com, tg...@linutronix.de, x...@kernel.org
Hello,

syzkaller hit the following crash on
9829d9f31f6c0e4984545e03032f14ccca6eeb68
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.

syzkaller reproducer is attached. See https://goo.gl/kgGztJ
for information about syzkaller reproducers


WARNING: CPU: 0 PID: 4003 at arch/x86/kvm/vmx.c:6526
handle_ept_misconfig+0x140/0x520 arch/x86/kvm/vmx.c:6526
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 4003 Comm: syz-executor1 Not tainted 4.13.0-next-20170904+ #14
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:16 [inline]
dump_stack+0x194/0x257 lib/dump_stack.c:52
panic+0x1e4/0x417 kernel/panic.c:181
__warn+0x1c4/0x1d9 kernel/panic.c:542
report_bug+0x211/0x2d0 lib/bug.c:183
fixup_bug+0x40/0x90 arch/x86/kernel/traps.c:178
do_trap_no_signal arch/x86/kernel/traps.c:212 [inline]
do_trap+0x260/0x390 arch/x86/kernel/traps.c:261
do_error_trap+0x120/0x390 arch/x86/kernel/traps.c:298
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:311
invalid_op+0x18/0x20 arch/x86/entry/entry_64.S:905
RIP: 0010:handle_ept_misconfig+0x140/0x520 arch/x86/kvm/vmx.c:6526
RSP: 0018:ffff88006d2df470 EFLAGS: 00010297
RAX: ffff88006d1d0540 RBX: 1ffff1000da5be90 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffed000da5be78
RBP: ffff88006d2df548 R08: 0000000000000007 R09: ffff88006d2df2f0
R10: ffff88006d1d0540 R11: 0000000000000002 R12: ffff88003aec06c0
R13: 00000000fffffff2 R14: ffff88006d2df520 R15: dffffc0000000000
vmx_handle_exit+0x24b/0x1a60 arch/x86/kvm/vmx.c:8823
vcpu_enter_guest arch/x86/kvm/x86.c:7038 [inline]
vcpu_run arch/x86/kvm/x86.c:7100 [inline]
kvm_arch_vcpu_ioctl_run+0x1d36/0x5a30 arch/x86/kvm/x86.c:7261
kvm_vcpu_ioctl+0x64c/0x1010 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2550
vfs_ioctl fs/ioctl.c:45 [inline]
do_vfs_ioctl+0x1b1/0x1530 fs/ioctl.c:685
SYSC_ioctl fs/ioctl.c:700 [inline]
SyS_ioctl+0x8f/0xc0 fs/ioctl.c:691
entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x447299
RSP: 002b:00007fddb74bdc08 EFLAGS: 00000296 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000000000b RCX: 0000000000447299
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000000b
RBP: 0000000000000082 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000296 R12: 000000000000000c
R13: 0000000000005790 R14: 00000000006e8850 R15: 000000000000000b
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.

syzbot will keep track of this bug report.
Once a fix for this bug is committed, please 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.
config.txt
raw.log
repro.txt

Dmitry Vyukov

unread,
Oct 26, 2017, 12:37:53 PM10/26/17
to syzbot, H. Peter Anvin, KVM list, LKML, Ingo Molnar, Paolo Bonzini, Radim Krčmář, syzkall...@googlegroups.com, Thomas Gleixner, x...@kernel.org
On Thu, Oct 26, 2017 at 6:35 PM, syzbot
<bot+c1d9517cab094dae65...@syzkaller.appspotmail.com>
wrote:
> Hello,
>
> syzkaller hit the following crash on
> 9829d9f31f6c0e4984545e03032f14ccca6eeb68
> 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.
>
> syzkaller reproducer is attached. See https://goo.gl/kgGztJ
> for information about syzkaller reproducers

This also happened on more recent commits including upstream
a957fd420ca8774f1a6708c64a867f056e67c46e and
8a5776a5f49812d29fe4b2d0a2d71675c3facf3f.
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-bugs/001a11440f66112544055c75c246%40google.com.
> For more options, visit https://groups.google.com/d/optout.

syzbot

unread,
Feb 6, 2018, 3:30:03 AM2/6/18
to dvy...@google.com, h...@zytor.com, k...@vger.kernel.org, linux-...@vger.kernel.org, mi...@redhat.com, pbon...@redhat.com, rkr...@redhat.com, syzkall...@googlegroups.com, tg...@linutronix.de, x...@kernel.org
syzbot has found reproducer for the following crash on upstream commit
2deb41b245320f0eefb535a5c8ea19ed66b33c04 (Mon Feb 5 18:07:40 2018 +0000)
Merge tag 'rproc-v4.16' of git://github.com/andersson/remoteproc

So far this crash happened 234 times on linux-next, mmots, upstream.
C reproducer is attached.
syzkaller reproducer is attached.
Raw console output is attached.
compiler: gcc (GCC) 7.1.1 20170620
.config is attached.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by:
syzbot+c1d9517cab094dae...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed.

WARNING: CPU: 0 PID: 4187 at arch/x86/kvm/vmx.c:6771
handle_ept_misconfig+0x140/0x520 arch/x86/kvm/vmx.c:6771
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 4187 Comm: syzkaller225100 Not tainted 4.15.0+ #298
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x194/0x257 lib/dump_stack.c:53
panic+0x1e4/0x41c kernel/panic.c:183
__warn+0x1dc/0x200 kernel/panic.c:547
report_bug+0x211/0x2d0 lib/bug.c:184
fixup_bug.part.11+0x37/0x80 arch/x86/kernel/traps.c:178
fixup_bug arch/x86/kernel/traps.c:247 [inline]
do_error_trap+0x2d7/0x3e0 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:315
invalid_op+0x22/0x40 arch/x86/entry/entry_64.S:984
RIP: 0010:handle_ept_misconfig+0x140/0x520 arch/x86/kvm/vmx.c:6771
RSP: 0018:ffff8801b2807360 EFLAGS: 00010293
RAX: ffff8801b2a16740 RBX: 1ffff10036500e6e RCX: ffffffff81193de0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffed0036500e58
RBP: ffff8801b2807438 R08: 0000000000000007 R09: ffff8801b28071d8
R10: ffff8801b2806f30 R11: 0000000000000002 R12: ffff8801c5618480
R13: 00000000fffffff2 R14: ffff8801b2807410 R15: dffffc0000000000
vmx_handle_exit+0x25d/0x1ce0 arch/x86/kvm/vmx.c:8955
vcpu_enter_guest arch/x86/kvm/x86.c:7083 [inline]
vcpu_run arch/x86/kvm/x86.c:7145 [inline]
kvm_arch_vcpu_ioctl_run+0x1c69/0x5bf0 arch/x86/kvm/x86.c:7312
kvm_vcpu_ioctl+0x64c/0x1010 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2564
vfs_ioctl fs/ioctl.c:46 [inline]
do_vfs_ioctl+0x1b1/0x1520 fs/ioctl.c:686
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x8f/0xc0 fs/ioctl.c:692
do_syscall_64+0x282/0x940 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x26/0x9b
RIP: 0033:0x448a79
RSP: 002b:00007ff13702fda8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000006ddc3c RCX: 0000000000448a79
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000011b
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000006ddc38
R13: 6d766b2f7665642f R14: 00007ff1370309c0 R15: 000000000000000d
raw.log.txt
repro.syz.txt
repro.c.txt
config.txt

Wanpeng Li

unread,
Feb 6, 2018, 3:58:10 AM2/6/18
to syzbot, Dmitry Vyukov, H. Peter Anvin, kvm, LKML, Ingo Molnar, Paolo Bonzini, Radim Krcmar, syzkall...@googlegroups.com, Thomas Gleixner, the arch/x86 maintainers
2018-02-06 16:30 GMT+08:00 syzbot
<syzbot+c1d9517cab094dae...@syzkaller.appspotmail.com>:
> syzbot has found reproducer for the following crash on upstream commit
> 2deb41b245320f0eefb535a5c8ea19ed66b33c04 (Mon Feb 5 18:07:40 2018 +0000)
> Merge tag 'rproc-v4.16' of git://github.com/andersson/remoteproc
>
> So far this crash happened 234 times on linux-next, mmots, upstream.
> C reproducer is attached.
> syzkaller reproducer is attached.
> Raw console output is attached.
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached.
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by:
> syzbot+c1d9517cab094dae...@syzkaller.appspotmail.com
> It will help syzbot understand when the bug is fixed.
>
> WARNING: CPU: 0 PID: 4187 at arch/x86/kvm/vmx.c:6771
> handle_ept_misconfig+0x140/0x520 arch/x86/kvm/vmx.c:6771
> Kernel panic - not syncing: panic_on_warn set ...

I can reproduce, will have a look.

Regards,
Wanpeng Li
Reply all
Reply to author
Forward
0 new messages