From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Gleb Natapov <gleb@kernel.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: nVMX: Unconditionally uninit the MMU on nested vmexit
Date: Thu, 2 Jan 2014 11:22:46 -0200 [thread overview]
Message-ID: <20140102132246.GA7080@amt.cnet> (raw)
In-Reply-To: <52BEEEE8.7080506@web.de>
On Sat, Dec 28, 2013 at 04:31:52PM +0100, Jan Kiszka wrote:
> Three reasons for doing this: 1. arch.walk_mmu points to arch.mmu anyway
> in case nested EPT wasn't in use. 2. this aligns VMX with SVM. But 3. is
> most important: nested_cpu_has_ept(vmcs12) queries the VMCS page, and if
> one guest VCPU manipulates the page of another VCPU in L2, we may be
> fooled to skip over the nested_ept_uninit_mmu_context, leaving mmu in
> nested state. That can crash the host later on if nested_ept_get_cr3 is
> invoked while L1 already left vmxon and nested.current_vmcs12 became
> NULL therefore.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> arch/x86/kvm/vmx.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index 1d9b0ec..48d0b46 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -8366,8 +8366,7 @@ static void load_vmcs12_host_state(struct kvm_vcpu *vcpu,
> vcpu->arch.cr4_guest_owned_bits = ~vmcs_readl(CR4_GUEST_HOST_MASK);
> kvm_set_cr4(vcpu, vmcs12->host_cr4);
>
> - if (nested_cpu_has_ept(vmcs12))
> - nested_ept_uninit_mmu_context(vcpu);
> + nested_ept_uninit_mmu_context(vcpu);
>
> kvm_set_cr3(vcpu, vmcs12->host_cr3);
> kvm_mmu_reset_context(vcpu);
> --
Applied to master branch, thanks.
prev parent reply other threads:[~2014-01-02 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 15:31 [PATCH] KVM: nVMX: Unconditionally uninit the MMU on nested vmexit Jan Kiszka
2014-01-02 13:22 ` Marcelo Tosatti [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=20140102132246.GA7080@amt.cnet \
--to=mtosatti@redhat.com \
--cc=gleb@kernel.org \
--cc=jan.kiszka@web.de \
--cc=kvm@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