From: syzbot <syzbot+01bc9e7a8a3f138b71cf@syzkaller.appspotmail.com>
To: dvyukov@google.com, hpa@zytor.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
pbonzini@redhat.com, rkrcmar@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: WARNING in free_loaded_vmcs (2)
Date: Mon, 03 Sep 2018 19:41:02 -0700 [thread overview]
Message-ID: <000000000000bc9ef905750296a4@google.com> (raw)
In-Reply-To: <000000000000b239d705736497a3@google.com>
syzbot has found a reproducer for the following crash on:
HEAD commit: 60c1f89241d4 Merge tag 'dma-mapping-4.19-2' of git://git.i..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15022d5a400000
kernel config: https://syzkaller.appspot.com/x/.config?x=4c7e83258d6e0156
dashboard link: https://syzkaller.appspot.com/bug?extid=01bc9e7a8a3f138b71cf
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12a6513e400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+01bc9e7a8a3f138b71cf@syzkaller.appspotmail.com
IPv6: ADDRCONF(NETDEV_UP): veth1: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
8021q: adding VLAN 0 to HW filter on device team0
L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and
https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html for details.
WARNING: CPU: 1 PID: 4980 at arch/x86/kvm/vmx.c:4754
free_loaded_vmcs+0x160/0x1b0 arch/x86/kvm/vmx.c:4754
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 4980 Comm: syz-executor0 Not tainted 4.19.0-rc2+ #220
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+0x1c9/0x2b4 lib/dump_stack.c:113
panic+0x238/0x4e7 kernel/panic.c:184
__warn.cold.8+0x163/0x1ba kernel/panic.c:536
report_bug+0x252/0x2d0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
do_error_trap+0x1fc/0x4d0 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:993
RIP: 0010:free_loaded_vmcs+0x160/0x1b0 arch/x86/kvm/vmx.c:4754
Code: 81 e8 44 be 53 00 48 89 da 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03
80 3c 02 00 75 49 4c 8b 23 e9 22 ff ff ff e8 80 fc 5f 00 <0f> 0b eb b0 e8
b7 f9 9e 00 e9 f4 fe ff ff 48 89 df e8 ca f9 9e 00
RSP: 0018:ffff8801d06af748 EFLAGS: 00010293
RAX: ffff8801d068a500 RBX: ffff8801d0ab57a8 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff811cd2a0 RDI: ffff8801d0ab57b0
RBP: ffff8801d06af760 R08: ffff8801d068a500 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8801c7166000
R13: 0000000000000001 R14: dffffc0000000000 R15: 0000000000000001
vmx_free_vcpu+0x204/0x300 arch/x86/kvm/vmx.c:10945
kvm_arch_vcpu_free arch/x86/kvm/x86.c:8420 [inline]
kvm_free_vcpus arch/x86/kvm/x86.c:8870 [inline]
kvm_arch_destroy_vm+0x365/0x7c0 arch/x86/kvm/x86.c:8967
kvm_destroy_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:752 [inline]
kvm_put_kvm+0x73f/0x1060 arch/x86/kvm/../../../virt/kvm/kvm_main.c:773
kvm_vcpu_release+0x7b/0xa0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2407
__fput+0x38a/0xa40 fs/file_table.c:278
____fput+0x15/0x20 fs/file_table.c:309
task_work_run+0x1e8/0x2a0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x318/0x380 arch/x86/entry/common.c:166
prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
syscall_return_slowpath arch/x86/entry/common.c:268 [inline]
do_syscall_64+0x6be/0x820 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x410c30
Code: 01 f0 ff ff 0f 83 60 19 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f
44 00 00 83 3d 5d 53 63 00 00 75 14 b8 03 00 00 00 0f 05 <48> 3d 01 f0 ff
ff 0f 83 34 19 00 00 c3 48 83 ec 08 e8 0a fc ff ff
RSP: 002b:00007ffeb3e8ae98 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000006 RCX: 0000000000410c30
RDX: 0000001b32e20000 RSI: 00000000007334f0 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000004129f0
R13: 0000000000412a80 R14: 0000000000000000 R15: badc0ffeebadface
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..
next prev parent reply other threads:[~2018-09-04 2:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 12:46 WARNING in free_loaded_vmcs (2) syzbot
2018-08-14 17:16 ` Paolo Bonzini
2018-08-14 20:41 ` Dmitry Vyukov
2018-08-21 16:42 ` Paolo Bonzini
2018-09-04 2:41 ` syzbot [this message]
2019-03-31 4:53 ` syzbot
2019-04-01 19:16 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000bc9ef905750296a4@google.com \
--to=syzbot+01bc9e7a8a3f138b71cf@syzkaller.appspotmail.com \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).