From: Sean Christopherson <seanjc@google.com>
To: Krish Sadhukhan <krish.sadhukhan@oracle.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, jmattson@google.com
Subject: Re: [PATCH 1/2 v4] KVM: nSVM: Check reserved values for 'Type' and invalid vectors in EVENTINJ
Date: Mon, 7 Dec 2020 12:17:29 -0800 [thread overview]
Message-ID: <X86N2c7ZG5fAToND@google.com> (raw)
In-Reply-To: <20201207194129.7543-2-krish.sadhukhan@oracle.com>
On Mon, Dec 07, 2020, Krish Sadhukhan wrote:
> According to sections "Canonicalization and Consistency Checks" and "Event
> Injection" in APM vol 2
>
> VMRUN exits with VMEXIT_INVALID error code if either:
> - Reserved values of TYPE have been specified, or
> - TYPE = 3 (exception) has been specified with a vector that does not
> correspond to an exception (this includes vector 2, which is an NMI,
> not an exception).
>
> Signed-off-by: Krish Sadhukhan <krish.sadhukhan@oracle.com>
> ---
> arch/x86/include/asm/svm.h | 4 ++++
> arch/x86/kvm/svm/nested.c | 14 ++++++++++++++
> 2 files changed, 18 insertions(+)
>
> diff --git a/arch/x86/include/asm/svm.h b/arch/x86/include/asm/svm.h
> index 71d630bb5e08..d676f140cd19 100644
> --- a/arch/x86/include/asm/svm.h
> +++ b/arch/x86/include/asm/svm.h
> @@ -341,9 +341,13 @@ struct vmcb {
> #define SVM_EVTINJ_TYPE_MASK (7 << SVM_EVTINJ_TYPE_SHIFT)
>
> #define SVM_EVTINJ_TYPE_INTR (0 << SVM_EVTINJ_TYPE_SHIFT)
> +#define SVM_EVTINJ_TYPE_RESV1 (1 << SVM_EVTINJ_TYPE_SHIFT)
> #define SVM_EVTINJ_TYPE_NMI (2 << SVM_EVTINJ_TYPE_SHIFT)
> #define SVM_EVTINJ_TYPE_EXEPT (3 << SVM_EVTINJ_TYPE_SHIFT)
> #define SVM_EVTINJ_TYPE_SOFT (4 << SVM_EVTINJ_TYPE_SHIFT)
> +#define SVM_EVTINJ_TYPE_RESV5 (5 << SVM_EVTINJ_TYPE_SHIFT)
> +#define SVM_EVTINJ_TYPE_RESV6 (6 << SVM_EVTINJ_TYPE_SHIFT)
> +#define SVM_EVTINJ_TYPE_RESV7 (7 << SVM_EVTINJ_TYPE_SHIFT)
>
> #define SVM_EVTINJ_VALID (1 << 31)
> #define SVM_EVTINJ_VALID_ERR (1 << 11)
> diff --git a/arch/x86/kvm/svm/nested.c b/arch/x86/kvm/svm/nested.c
> index 9e4c226dbf7d..fa51231c1f24 100644
> --- a/arch/x86/kvm/svm/nested.c
> +++ b/arch/x86/kvm/svm/nested.c
> @@ -212,6 +212,9 @@ static bool svm_get_nested_state_pages(struct kvm_vcpu *vcpu)
>
> static bool nested_vmcb_check_controls(struct vmcb_control_area *control)
> {
> + u8 type, vector;
> + bool valid;
> +
> if ((vmcb_is_intercept(control, INTERCEPT_VMRUN)) == 0)
> return false;
>
> @@ -222,6 +225,17 @@ static bool nested_vmcb_check_controls(struct vmcb_control_area *control)
> !npt_enabled)
> return false;
>
> + valid = control->event_inj & SVM_EVTINJ_VALID;
> + type = control->event_inj & SVM_EVTINJ_TYPE_MASK;
The mask is shifted by 8, which means type is guaranteed to be 0 since the value
will be truncated when casting to a u8. I'm somewhat surprised neither
checkpatch nor checkpatch warns. The types are also shifted, so the easiest
thing is probably to store it as a u32, same as event_inj. I suspect your test
passes because type==0 is INTR and the test always injects #DE, which is likely
an illegal vector.
> + if (valid && (type == SVM_EVTINJ_TYPE_RESV1 ||
> + type >= SVM_EVTINJ_TYPE_RESV5))
> + return false;
> +
> + vector = control->event_inj & SVM_EVTINJ_VEC_MASK;
> + if (valid && (type == SVM_EVTINJ_TYPE_EXEPT))
> + if (vector == NMI_VECTOR || vector > 31)
Preferred style is to combine these into a single statement.
> + return false;
> +
> return true;
> }
>
> --
> 2.27.0
>
next prev parent reply other threads:[~2020-12-07 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 19:41 [PATCH 0/2 v4] KVM: nSVM: Check reserved values for 'Type' and invalid vectors in EVENTINJ Krish Sadhukhan
2020-12-07 19:41 ` [PATCH 1/2 " Krish Sadhukhan
2020-12-07 20:17 ` Sean Christopherson [this message]
2020-12-11 21:44 ` Krish Sadhukhan
2020-12-11 21:49 ` Paolo Bonzini
2020-12-07 19:41 ` [PATCH 2/2 v4] nSVM: Test " Krish Sadhukhan
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=X86N2c7ZG5fAToND@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=krish.sadhukhan@oracle.com \
--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