All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Euan Harris <euan.harris@citrix.com>, xen-devel@lists.xenproject.org
Cc: kevin.tian@intel.com, jun.nakajima@intel.com, jbeulich@suse.com
Subject: Re: [PATCH 0/2] Validate host VMX MSRs before accessing them
Date: Mon, 13 Jun 2016 13:13:18 +0100	[thread overview]
Message-ID: <575EA35E.10408@citrix.com> (raw)
In-Reply-To: <1465467250-8742-1-git-send-email-euan.harris@citrix.com>

On 09/06/16 11:14, Euan Harris wrote:
> nvmx_msr_read_intercept() does not check the prerequisites before
> accessing MSR_IA32_VMX_PROCBASED_CTLS2, MSR_IA32_VMX_EPT_VPID_CAP,
> MSR_IA32_VMX_VMFUNC on the host.   Accessing these MSRs from a nested
> VMX guest running on a host which does not support them will cause
> Xen to crash with a GPF.
>
> Euan Harris (2):
>   nested vmx: Fix comment typos in nvmx_msr_read_intercept()
>   nested vmx: Validate host VMX MSRs before accessing them
>
>  xen/arch/x86/hvm/vmx/vvmx.c |   32 +++++++++++++++++++++++---------
>  1 file changed, 23 insertions(+), 9 deletions(-)
>

Committed, with the indicated fixup.

Thanks,

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      parent reply	other threads:[~2016-06-13 12:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 10:14 [PATCH 0/2] Validate host VMX MSRs before accessing them Euan Harris
2016-06-09 10:14 ` [PATCH 1/2] nested vmx: Fix comment typos in nvmx_msr_read_intercept() Euan Harris
2016-06-12  7:37   ` Tian, Kevin
2016-06-09 10:14 ` [PATCH 2/2] nested vmx: Validate host VMX MSRs before accessing them Euan Harris
2016-06-09 12:47   ` Jan Beulich
2016-06-09 13:20     ` Euan Harris
2016-06-12  7:39       ` Tian, Kevin
2016-06-13 12:13 ` Andrew Cooper [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=575EA35E.10408@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=euan.harris@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.