From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+c1cbaedc2613058d5194@syzkaller.appspotmail.com
Subject: [PATCH 0/4] KVM: x86: Fix WFS vs. pending SMI WARN
Date: Thu, 5 Jun 2025 12:50:14 -0700 [thread overview]
Message-ID: <20250605195018.539901-1-seanjc@google.com> (raw)
Fix a user-triggerable WARN that syzkaller found by stuffing INIT_RECEIVED,
a.k.a. WFS, and then putting the vCPU into VMX Root Mode (post-VMXON). Use
the same approach KVM uses for dealing with "impossible" emulation when
running a !URG guest, and simply wait until KVM_RUN to detect that the vCPU
has architecturally impossible state.
Sean Christopherson (4):
KVM: x86: Drop pending_smi vs. INIT_RECEIVED check when setting
MP_STATE
KVM: x86: WARN and reject KVM_RUN if vCPU's MP_STATE is SIPI_RECEIVED
KVM: x86: Move INIT_RECEIVED vs. INIT/SIPI blocked check to KVM_RUN
KVM: x86: Refactor handling of SIPI_RECEIVED when setting MP_STATE
arch/x86/kvm/x86.c | 49 ++++++++++++++++++++++++++++------------------
1 file changed, 30 insertions(+), 19 deletions(-)
base-commit: 61374cc145f4a56377eaf87c7409a97ec7a34041
--
2.50.0.rc0.604.gd4ff7b7c86-goog
next reply other threads:[~2025-06-05 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 19:50 Sean Christopherson [this message]
2025-06-05 19:50 ` [PATCH 1/4] KVM: x86: Drop pending_smi vs. INIT_RECEIVED check when setting MP_STATE Sean Christopherson
2025-06-05 19:50 ` [PATCH 2/4] KVM: x86: WARN and reject KVM_RUN if vCPU's MP_STATE is SIPI_RECEIVED Sean Christopherson
2025-06-05 19:50 ` [PATCH 3/4] KVM: x86: Move INIT_RECEIVED vs. INIT/SIPI blocked check to KVM_RUN Sean Christopherson
2025-06-05 19:50 ` [PATCH 4/4] KVM: x86: Refactor handling of SIPI_RECEIVED when setting MP_STATE Sean Christopherson
2025-06-24 19:38 ` [PATCH 0/4] KVM: x86: Fix WFS vs. pending SMI WARN 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=20250605195018.539901-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=syzbot+c1cbaedc2613058d5194@syzkaller.appspotmail.com \
/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