mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Huang, Kai" <kai.huang@intel.com>
To: "pbonzini@redhat.com" <pbonzini@redhat.com>, "Christopherson,,
	Sean" <seanjc@google.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: VMX: Resume guest immediately when injecting #GP on ECREATE
Date: Mon, 3 Oct 2022 01:01:18 +0000	[thread overview]
Message-ID: <a3b7068c376ba01d4bd715ce549932ce052eca42.camel@intel.com> (raw)
In-Reply-To: <20220930233132.1723330-1-seanjc@google.com>

On Fri, 2022-09-30 at 23:31 +0000, Sean Christopherson wrote:
> Resume the guest immediately when injecting a #GP on ECREATE due to an
> invalid enclave size, i.e. don't attempt ECREATE in the host.  The #GP is
> a terminal fault, e.g. skipping the instruction if ECREATE is successful
> would result in KVM injecting #GP on the instruction following ECREATE.
> 
> Fixes: 70210c044b4e ("KVM: VMX: Add SGX ENCLS[ECREATE] handler to enforce CPUID restrictions")
> Cc: stable@vger.kernel.org
> Cc: Kai Huang <kai.huang@intel.com>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> 
> Effectively compile tested only, found by inspection when auditing use of
> kvm_skip_emulated_instruction().
> 
>  arch/x86/kvm/vmx/sgx.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kvm/vmx/sgx.c b/arch/x86/kvm/vmx/sgx.c
> index 8f95c7c01433..b12da2a6dec9 100644
> --- a/arch/x86/kvm/vmx/sgx.c
> +++ b/arch/x86/kvm/vmx/sgx.c
> @@ -182,8 +182,10 @@ static int __handle_encls_ecreate(struct kvm_vcpu *vcpu,
>  	/* Enforce CPUID restriction on max enclave size. */
>  	max_size_log2 = (attributes & SGX_ATTR_MODE64BIT) ? sgx_12_0->edx >> 8 :
>  							    sgx_12_0->edx;
> -	if (size >= BIT_ULL(max_size_log2))
> +	if (size >= BIT_ULL(max_size_log2)) {
>  		kvm_inject_gp(vcpu, 0);
> +		return 1;
> +	}
>  
>  	/*
>  	 * sgx_virt_ecreate() returns:
> 
> base-commit: c59fb127583869350256656b7ed848c398bef879
> -- 
> 2.38.0.rc1.362.ged0d419d3c-goog
> 


Thanks Sean.

Reviewed-by: Kai Huang <kai.huang@intel.com>

-- 
Thanks,
-Kai



      reply	other threads:[~2022-10-03  1:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 23:31 Sean Christopherson
2022-10-03  1:01 ` Huang, Kai [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=a3b7068c376ba01d4bd715ce549932ce052eca42.camel@intel.com \
    --to=kai.huang@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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®