From: Maxim Levitsky <mlevitsk@redhat.com>
To: Emanuele Giuseppe Esposito <eesposit@redhat.com>, kvm@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 4/7] nSVM: use vmcb_save_area_cached in nested_vmcb_valid_sregs()
Date: Wed, 03 Nov 2021 19:03:54 +0200 [thread overview]
Message-ID: <9743cd8aa1e2dd8ddb0caa1be1de608fb19c19d6.camel@redhat.com> (raw)
In-Reply-To: <20211103140527.752797-5-eesposit@redhat.com>
On Wed, 2021-11-03 at 10:05 -0400, Emanuele Giuseppe Esposito wrote:
> Now that struct vmcb_save_area_cached contains the required
> vmcb fields values (done in nested_load_save_from_vmcb12()),
> check them to see if they are correct in nested_vmcb_valid_sregs().
>
> While at it, rename nested_vmcb_valid_sregs in nested_vmcb_check_save.
> _nested_vmcb_check_save takes the additional @save parameter, so it
> is helpful when we want to check a non-svm save state, like in
> svm_set_nested_state. The reason for that is that save is the L1
> state, not L2, so we just check it.
>
> Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
> ---
> arch/x86/kvm/svm/nested.c | 18 ++++++++++++++----
> 1 file changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/kvm/svm/nested.c b/arch/x86/kvm/svm/nested.c
> index 162b338a6c74..64fb43234e06 100644
> --- a/arch/x86/kvm/svm/nested.c
> +++ b/arch/x86/kvm/svm/nested.c
> @@ -245,8 +245,8 @@ static bool nested_vmcb_check_controls(struct kvm_vcpu *vcpu,
> }
>
> /* Common checks that apply to both L1 and L2 state. */
> -static bool nested_vmcb_valid_sregs(struct kvm_vcpu *vcpu,
> - struct vmcb_save_area *save)
> +static bool _nested_vmcb_check_save(struct kvm_vcpu *vcpu,
> + struct vmcb_save_area_cached *save)
> {
> /*
> * FIXME: these should be done after copying the fields,
> @@ -286,6 +286,14 @@ static bool nested_vmcb_valid_sregs(struct kvm_vcpu *vcpu,
> return true;
> }
>
> +static bool nested_vmcb_check_save(struct kvm_vcpu *vcpu)
> +{
> + struct vcpu_svm *svm = to_svm(vcpu);
> + struct vmcb_save_area_cached *save = &svm->nested.save;
> +
> + return _nested_vmcb_check_save(vcpu, save);
> +}
> +
> static
> void _nested_copy_vmcb_control_to_cache(struct vmcb_control_area *to,
> struct vmcb_control_area *from)
> @@ -694,7 +702,7 @@ int nested_svm_vmrun(struct kvm_vcpu *vcpu)
> nested_copy_vmcb_control_to_cache(svm, &vmcb12->control);
> nested_copy_vmcb_save_to_cache(svm, &vmcb12->save);
>
> - if (!nested_vmcb_valid_sregs(vcpu, &vmcb12->save) ||
> + if (!nested_vmcb_check_save(vcpu) ||
> !nested_vmcb_check_controls(vcpu, &svm->nested.ctl)) {
> vmcb12->control.exit_code = SVM_EXIT_ERR;
> vmcb12->control.exit_code_hi = 0;
> @@ -1330,6 +1338,7 @@ static int svm_set_nested_state(struct kvm_vcpu *vcpu,
> &user_kvm_nested_state->data.svm[0];
> struct vmcb_control_area *ctl;
> struct vmcb_save_area *save;
> + struct vmcb_save_area_cached save_cached;
> unsigned long cr0;
> int ret;
>
> @@ -1397,10 +1406,11 @@ static int svm_set_nested_state(struct kvm_vcpu *vcpu,
> * Validate host state saved from before VMRUN (see
> * nested_svm_check_permissions).
> */
> + _nested_copy_vmcb_save_to_cache(&save_cached, save);
Nitpick: here I would probalby add a comment that we are dealing here with L1
save area and we just want to check it and not cache it.
Also suddenly the name _nested_copy_vmcb_save_to_cache sounds a bit off,
but I don't have any better idea so I don't mind leaving it as is.
Anyway,
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Best regards,
Maxim Levitsky
> if (!(save->cr0 & X86_CR0_PG) ||
> !(save->cr0 & X86_CR0_PE) ||
> (save->rflags & X86_EFLAGS_VM) ||
> - !nested_vmcb_valid_sregs(vcpu, save))
> + !_nested_vmcb_check_save(vcpu, &save_cached))
> goto out_free;
>
> /*
next prev parent reply other threads:[~2021-11-03 17:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 14:05 [PATCH v5 0/7] KVM: nSVM: avoid TOC/TOU race when checking vmcb12 Emanuele Giuseppe Esposito
2021-11-03 14:05 ` [PATCH v5 1/7] KVM: nSVM: move nested_vmcb_check_cr3_cr4 logic in nested_vmcb_valid_sregs Emanuele Giuseppe Esposito
2021-11-03 14:05 ` [PATCH v5 2/7] nSVM: introduce smv->nested.save to cache save area fields Emanuele Giuseppe Esposito
2021-11-03 17:02 ` Maxim Levitsky
2021-11-11 13:52 ` Paolo Bonzini
2021-11-12 7:43 ` Maxim Levitsky
2021-11-03 14:05 ` [PATCH v5 3/7] nSVM: rename nested_load_control_from_vmcb12 in nested_copy_vmcb_control_to_cache Emanuele Giuseppe Esposito
2021-11-03 17:03 ` Maxim Levitsky
2021-11-03 14:05 ` [PATCH v5 4/7] nSVM: use vmcb_save_area_cached in nested_vmcb_valid_sregs() Emanuele Giuseppe Esposito
2021-11-03 17:03 ` Maxim Levitsky [this message]
2021-11-03 14:05 ` [PATCH v5 5/7] nSVM: use svm->nested.save to load vmcb12 registers and avoid TOC/TOU races Emanuele Giuseppe Esposito
2021-11-03 14:05 ` [PATCH v5 6/7] nSVM: introduce struct vmcb_ctrl_area_cached Emanuele Giuseppe Esposito
2021-11-03 14:05 ` [PATCH v5 7/7] nSVM: use vmcb_ctrl_area_cached instead of vmcb_control_area in struct svm_nested_state Emanuele Giuseppe Esposito
2021-11-03 17:05 ` Maxim Levitsky
2021-11-11 13:55 ` [PATCH v5 0/7] KVM: nSVM: avoid TOC/TOU race when checking vmcb12 Paolo Bonzini
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=9743cd8aa1e2dd8ddb0caa1be1de608fb19c19d6.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=bp@alien8.de \
--cc=eesposit@redhat.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@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