public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Document an erratum in KVM_SET_VCPU_EVENTS on Intel CPUs
Date: Fri, 1 Nov 2024 12:24:13 -0700	[thread overview]
Message-ID: <ZyUq3WSLbKkoiExF@google.com> (raw)
In-Reply-To: <173039507056.1509043.12101873900724716741.b4-ty@google.com>

On Thu, Oct 31, 2024, Sean Christopherson wrote:
> On Fri, 02 Aug 2024 13:04:20 -0700, Sean Christopherson wrote:
> > Document a flaw in KVM's ABI which lets userspace attempt to inject a
> > "bad" hardware exception event, and thus induce VM-Fail on Intel CPUs.
> > Fixing the flaw is a fool's errand, as AMD doesn't sanity check the
> > validity of the error code, Intel CPUs that support CET relax the check
> > for Protected Mode, userspace can change the mode after queueing an
> > exception, KVM ignores the error code when emulating Real Mode exceptions,
> > and so on and so forth.
> > 
> > [...]
> 
> Applied to kvm-x86 misc, thanks!
> 
> [1/1] KVM: x86: Document an erratum in KVM_SET_VCPU_EVENTS on Intel CPUs
>       https://github.com/kvm-x86/linux/commit/eebc1cfae6c9

FYI, I rebased misc to v6.12-rc5, as patches in another series had already been
taken through the tip tree.  New hash:

[1/1] KVM: x86: Document an erratum in KVM_SET_VCPU_EVENTS on Intel CPUs
      https://github.com/kvm-x86/linux/commit/0e3b70aa137c

      reply	other threads:[~2024-11-01 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 20:04 [PATCH] KVM: x86: Document an erratum in KVM_SET_VCPU_EVENTS on Intel CPUs Sean Christopherson
2024-10-31 19:51 ` Sean Christopherson
2024-11-01 19:24   ` Sean Christopherson [this message]

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=ZyUq3WSLbKkoiExF@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.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