From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+f1d2136db9c80d4733e8@syzkaller.appspotmail.com,
Maxim Levitsky <mlevitsk@redhat.com>
Subject: Re: [PATCH 0/4] KVM: VMX: Fix handling of invalid L2 guest state
Date: Thu, 9 Dec 2021 12:26:09 +0100 [thread overview]
Message-ID: <b3f9f46d-a424-a58c-e503-9069f46585f3@redhat.com> (raw)
In-Reply-To: <20211207193006.120997-1-seanjc@google.com>
On 12/7/21 20:30, Sean Christopherson wrote:
> Fixes and a test for invalid L2 guest state. TL;DR: KVM should never
> emulate L2 if L2's guest state is invalid.
>
> Patch 01 fixes a regression found by syzbot. Patch 02 closes what I suspect
> was the hole the buggy patch was trying to close. Patch 03 is a related
> docs update. Patch 04 is a selftest for the regression and for a subset
> of patch 02's behavior.
>
> Sean Christopherson (4):
> KVM: VMX: Always clear vmx->fail on emulation_required
> KVM: nVMX: Synthesize TRIPLE_FAULT for L2 if emulation is required
> KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state
> KVM: selftests: Add test to verify TRIPLE_FAULT on invalid L2 guest
> state
>
> .../admin-guide/kernel-parameters.txt | 8 +-
> arch/x86/kvm/vmx/vmx.c | 36 ++++--
> tools/testing/selftests/kvm/.gitignore | 1 +
> tools/testing/selftests/kvm/Makefile | 1 +
> .../x86_64/vmx_invalid_nested_guest_state.c | 105 ++++++++++++++++++
> 5 files changed, 138 insertions(+), 13 deletions(-)
> create mode 100644 tools/testing/selftests/kvm/x86_64/vmx_invalid_nested_guest_state.c
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2021-12-09 11:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 19:30 Sean Christopherson
2021-12-07 19:30 ` [PATCH 1/4] KVM: VMX: Always clear vmx->fail on emulation_required Sean Christopherson
2021-12-14 9:12 ` Maxim Levitsky
2021-12-07 19:30 ` [PATCH 2/4] KVM: nVMX: Synthesize TRIPLE_FAULT for L2 if emulation is required Sean Christopherson
2021-12-14 9:12 ` Maxim Levitsky
2021-12-07 19:30 ` [PATCH 3/4] KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state Sean Christopherson
2021-12-14 9:12 ` Maxim Levitsky
2021-12-07 19:30 ` [PATCH 4/4] KVM: selftests: Add test to verify TRIPLE_FAULT on invalid L2 guest state Sean Christopherson
2021-12-14 9:15 ` Maxim Levitsky
2021-12-09 11:26 ` Paolo Bonzini [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=b3f9f46d-a424-a58c-e503-9069f46585f3@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=seanjc@google.com \
--cc=syzbot+f1d2136db9c80d4733e8@syzkaller.appspotmail.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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®