[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YfBb5YU4adUAptUg@google.com>
Date: Tue, 25 Jan 2022 20:21:57 +0000
From: Sean Christopherson <seanjc@...gle.com>
To: syzbot <syzbot+8112db3ab20e70d50c31@...kaller.appspotmail.com>
Cc: bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com,
jmattson@...gle.com, joro@...tes.org, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, mingo@...hat.com,
pbonzini@...hat.com, syzkaller-bugs@...glegroups.com,
tglx@...utronix.de, vkuznets@...hat.com, wanpengli@...cent.com,
x86@...nel.org
Subject: Re: [syzbot] WARNING in free_loaded_vmcs (3)
On Mon, Jan 24, 2022, syzbot wrote:
> WARNING: CPU: 0 PID: 3606 at arch/x86/kvm/vmx/vmx.c:2665 free_loaded_vmcs arch/x86/kvm/vmx/vmx.c:2665 [inline]
> WARNING: CPU: 0 PID: 3606 at arch/x86/kvm/vmx/vmx.c:2665 free_loaded_vmcs+0x158/0x1a0 arch/x86/kvm/vmx/vmx.c:2656
KVM gets confused if userspace abuses KVM_SET_VCPU_EVENTS to toggle SMM on/off
while the vCPU is post-VMXON, I'll send a patch.
Powered by blists - more mailing lists