From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix GDT limit corruption on Intel
Date: Tue, 27 Jul 2010 21:25:49 -0300 [thread overview]
Message-ID: <20100728002549.GB7327@amt.cnet> (raw)
In-Reply-To: <1280158359-26593-1-git-send-email-avi@redhat.com>
On Mon, Jul 26, 2010 at 06:32:37PM +0300, Avi Kivity wrote:
> Intel vmx does not restore GDT.LIMIT; this allows host userspace to look at
> some host kernel bits by loading a segment register and looking whether a
> trap happened or not.
>
> Fix that by reloading GDT on heavyweight exits.
>
> Avi Kivity (2):
> KVM: VMX: Fix host GDT.LIMIT corruption
> KVM: VMX: Use host_gdt variable wherever we need the host gdt
>
> arch/x86/kvm/vmx.c | 19 ++++++++++---------
> 1 files changed, 10 insertions(+), 9 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2010-07-28 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 15:32 [PATCH 0/2] Fix GDT limit corruption on Intel Avi Kivity
2010-07-26 15:32 ` [PATCH 1/2] KVM: VMX: Fix host GDT.LIMIT corruption Avi Kivity
2010-07-26 15:32 ` [PATCH 2/2] KVM: VMX: Use host_gdt variable wherever we need the host gdt Avi Kivity
2010-07-28 0:25 ` 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=20100728002549.GB7327@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.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