From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216033] KVM VMX nested virtualization: VMXON does not check guest CR0 against IA32_VMX_CR0_FIXED0
Date: Fri, 02 Sep 2022 20:57:18 +0000 [thread overview]
Message-ID: <bug-216033-28872-eFjeS2nk5C@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216033-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216033
--- Comment #5 from Sean Christopherson (seanjc@google.com) ---
On Fri, Sep 02, 2022, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=216033
>
> --- Comment #4 from Eric Li (ercli@ucdavis.edu) ---
> > if (!nested_host_cr0_valid(vcpu, kvm_read_cr0(vcpu)) ||
> > !nested_host_cr4_valid(vcpu, kvm_read_cr4(vcpu))) {
> > kvm_queue_exception(vcpu, UD_VECTOR);
> > return 1;
> > }
>
> Thanks for the reply. I think there is still a typo. Do you mean the
> following?
Yes, yes I did.
> if (!nested_host_cr0_valid(vcpu, kvm_read_cr0(vcpu)) ||
> !nested_host_cr4_valid(vcpu, kvm_read_cr4(vcpu))) {
> kvm_queue_exception_e(vcpu, GP_VECTOR, 0);
> return 1;
> }
>
> Or maybe:
>
> if (!nested_host_cr0_valid(vcpu, kvm_read_cr0(vcpu)) ||
> !nested_host_cr4_valid(vcpu, kvm_read_cr4(vcpu))) {
> kvm_inject_gp(vcpu, 0);
> return 1;
> }
>
> I am not familiar with KVM code
Heh, for all the good that being familiar with KVM is doing me.
> so not sure which one should be used. Thanks again!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2022-09-02 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 3:54 [Bug 216033] New: KVM VMX nested virtualization: VMXON does not check guest CR0 against IA32_VMX_CR0_FIXED0 bugzilla-daemon
2022-05-26 16:18 ` [Bug 216033] " bugzilla-daemon
2022-09-02 18:39 ` bugzilla-daemon
2022-09-02 19:00 ` bugzilla-daemon
2022-09-02 19:45 ` bugzilla-daemon
2022-09-02 20:57 ` bugzilla-daemon [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=bug-216033-28872-eFjeS2nk5C@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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 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.