From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, BuraphaLinux Server <buraphalinuxserver@gmail.com>
Subject: Re: [PATCH] KVM: VMX: Fix host MSR_KERNEL_GS_BASE corruption
Date: Tue, 6 Jul 2010 15:39:25 -0300 [thread overview]
Message-ID: <20100706183925.GA20663@amt.cnet> (raw)
In-Reply-To: <1278405361-12517-1-git-send-email-avi@redhat.com>
On Tue, Jul 06, 2010 at 11:36:01AM +0300, Avi Kivity wrote:
> enter_lmode() and exit_lmode() modify the guest's EFER.LMA before calling
> vmx_set_efer(). However, the latter function depends on the value of EFER.LMA
> to determine whether MSR_KERNEL_GS_BASE needs reloading, via
> vmx_load_host_state(). With EFER.LMA changing under its feet, it took the
> wrong choice and corrupted userspace's %gs.
>
> This causes 32-on-64 host userspace to fault.
>
> Fix not touching EFER.LMA; instead ask vmx_set_efer() to change it.
>
> Signed-off-by: Avi Kivity <avi@redhat.com>
> ---
> arch/x86/kvm/vmx.c | 7 ++-----
> 1 files changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index ebaaeaf..2fdcc98 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -1812,18 +1812,15 @@ static void enter_lmode(struct kvm_vcpu *vcpu)
> (guest_tr_ar & ~AR_TYPE_MASK)
> | AR_TYPE_BUSY_64_TSS);
> }
> - vcpu->arch.efer |= EFER_LMA;
> - vmx_set_efer(vcpu, vcpu->arch.efer);
> + vmx_set_efer(vcpu, vcpu->arch.efer | EFER_LMA);
> }
>
> static void exit_lmode(struct kvm_vcpu *vcpu)
> {
> - vcpu->arch.efer &= ~EFER_LMA;
> -
> vmcs_write32(VM_ENTRY_CONTROLS,
> vmcs_read32(VM_ENTRY_CONTROLS)
> & ~VM_ENTRY_IA32E_MODE);
> - vmx_set_efer(vcpu, vcpu->arch.efer);
> + vmx_set_efer(vcpu, vcpu->arch.efer & ~EFER_LMA);
> }
>
> #endif
> --
> 1.7.1
Looks good.
prev parent reply other threads:[~2010-07-06 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 8:36 [PATCH] KVM: VMX: Fix host MSR_KERNEL_GS_BASE corruption Avi Kivity
2010-07-06 18:39 ` 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=20100706183925.GA20663@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=buraphalinuxserver@gmail.com \
--cc=kvm@vger.kernel.org \
/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