WARNING in handle_desc (2)

12 views
Skip to first unread message

syzbot

unread,
Sep 4, 2020, 4:19:15 AM9/4/20
to b...@alien8.de, h...@zytor.com, jmat...@google.com, jo...@8bytes.org, k...@vger.kernel.org, linux-...@vger.kernel.org, mi...@redhat.com, pbon...@redhat.com, sean.j.chr...@intel.com, syzkall...@googlegroups.com, tg...@linutronix.de, vkuz...@redhat.com, wanp...@tencent.com, x...@kernel.org
Hello,

syzbot found the following issue on:

HEAD commit: dcc5c6f0 Merge tag 'x86-urgent-2020-08-30' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1483ac85900000
kernel config: https://syzkaller.appspot.com/x/.config?x=978db74cb30aa994
dashboard link: https://syzkaller.appspot.com/bug?extid=6157aa3cd948b7a811ab
compiler: gcc (GCC) 10.1.0-syz 20200507

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

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 32353 at arch/x86/kvm/vmx/vmx.c:4965 handle_desc+0x5a/0x70 arch/x86/kvm/vmx/vmx.c:4965
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 32353 Comm: syz-executor.4 Not tainted 5.9.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x198/0x1fd lib/dump_stack.c:118
panic+0x347/0x7c0 kernel/panic.c:231
__warn.cold+0x20/0x46 kernel/panic.c:600
report_bug+0x1bd/0x210 lib/bug.c:198
handle_bug+0x38/0x90 arch/x86/kernel/traps.c:234
exc_invalid_op+0x14/0x40 arch/x86/kernel/traps.c:254
asm_exc_invalid_op+0x12/0x20 arch/x86/include/asm/idtentry.h:536
RIP: 0010:handle_desc+0x5a/0x70 arch/x86/kvm/vmx/vmx.c:4965
Code: ff 81 e3 00 08 00 00 48 89 de e8 91 c5 59 00 48 85 db 74 11 e8 e7 c8 59 00 48 89 ef 5b 31 f6 5d e9 db 87 f4 ff e8 d6 c8 59 00 <0f> 0b eb e6 e8 1d db 99 00 eb c3 90 66 2e 0f 1f 84 00 00 00 00 00
RSP: 0018:ffffc90017d67b98 EFLAGS: 00010216
RAX: 00000000000033f4 RBX: 0000000000000000 RCX: ffffc90010d96000
RDX: 0000000000040000 RSI: ffffffff811a822a RDI: 0000000000000007
RBP: ffff8880973d83c0 R08: 0000000000000000 R09: ffffffff8c5f1ac7
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff811a81d0
R13: ffff8880973d83f8 R14: 000000000000002e R15: 0000000000000000
vmx_handle_exit+0x293/0x14c0 arch/x86/kvm/vmx/vmx.c:6118
vcpu_enter_guest+0x18f4/0x3c20 arch/x86/kvm/x86.c:8638
vcpu_run arch/x86/kvm/x86.c:8703 [inline]
kvm_arch_vcpu_ioctl_run+0x440/0x1780 arch/x86/kvm/x86.c:8920
kvm_vcpu_ioctl+0x467/0xdf0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3230
vfs_ioctl fs/ioctl.c:48 [inline]
__do_sys_ioctl fs/ioctl.c:753 [inline]
__se_sys_ioctl fs/ioctl.c:739 [inline]
__x64_sys_ioctl+0x193/0x200 fs/ioctl.c:739
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45d5b9
Code: 5d b4 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 2b b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f925f9c9c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000011880 RCX: 000000000045d5b9
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000006
RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
R13: 00007ffc7b03146f R14: 00007f925f9ca9c0 R15: 000000000118cf4c
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Dec 29, 2020, 3:10:12 AM12/29/20
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages