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,
Michal Luczaj <mhal@rbox.co>
Subject: Re: [PATCH 0/2] KVM: selftests: Fix sync_regs race tests on AMD
Date: Fri, 25 Aug 2023 12:01:42 -0700 [thread overview]
Message-ID: <169297947911.2871633.4127274459666234045.b4-ty@google.com> (raw)
In-Reply-To: <20230817233430.1416463-1-seanjc@google.com>
On Thu, 17 Aug 2023 16:34:28 -0700, Sean Christopherson wrote:
> The recently introduced sync_regs subtests to detect TOCTOU bugs hang on
> AMD because KVM synthesizes INIT on triple fault shutdown (because AMD says
> the VMCB is undefined after shutdown). Fix it by loading known good state
> if a shutdown occurs.
>
> Patch two explicitly injects #UD as the "good" vector so that the test
> doesn't rely on KVM inadvertantly setting the vector to #DE (old, buggy
> behavior).
>
> [...]
Applied to kvm-x86 selftests.
[1/2] KVM: selftests: Reload "good" vCPU state if vCPU hits shutdown
https://github.com/kvm-x86/linux/commit/5002b112a5ad
[2/2] KVM: selftests: Explicit set #UD when *potentially* injecting exception
https://github.com/kvm-x86/linux/commit/02dc2543e379
--
https://github.com/kvm-x86/linux/tree/next
https://github.com/kvm-x86/linux/tree/fixes
prev parent reply other threads:[~2023-08-25 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 23:34 Sean Christopherson
2023-08-17 23:34 ` [PATCH 1/2] KVM: selftests: Reload "good" vCPU state if vCPU hits shutdown Sean Christopherson
2023-08-17 23:34 ` [PATCH 2/2] KVM: selftests: Explicit set #UD when *potentially* injecting exception Sean Christopherson
2023-08-25 19:01 ` 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=169297947911.2871633.4127274459666234045.b4-ty@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--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
all inboxes | Powered by JetHome®