All of lore.kernel.org
 help / color / mirror / Atom feed
From: Venkatesh Srinivas <venkateshs@chromium.org>
To: kvm@vger.kernel.org
Cc: seanjc@google.com, marcorr@google.com, venkateshs@chromium.org
Subject: [PATCH v2 2/2] KVM: Inject #GP on invalid writes to x2APIC registers
Date: Wed, 25 May 2022 17:39:33 +0000	[thread overview]
Message-ID: <20220525173933.1611076-2-venkateshs@chromium.org> (raw)
In-Reply-To: <20220525173933.1611076-1-venkateshs@chromium.org>

From: Marc Orr <marcorr@google.com>

From: Venkatesh Srinivas <venkateshs@chromium.org>

The upper bytes of any x2APIC register are reserved. Inject a #GP
into the guest if any of these reserved bits are set.

Signed-off-by: Marc Orr <marcorr@google.com>
Signed-off-by: Venkatesh Srinivas <venkateshs@chromium.org>
---
 arch/x86/kvm/lapic.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
index 6f8522e8c492..617e4936c5cc 100644
--- a/arch/x86/kvm/lapic.c
+++ b/arch/x86/kvm/lapic.c
@@ -2907,6 +2907,8 @@ int kvm_x2apic_msr_write(struct kvm_vcpu *vcpu, u32 msr, u64 data)
 
 	if (!lapic_in_kernel(vcpu) || !apic_x2apic_mode(apic))
 		return 1;
+	else if (data >> 32)
+		return 1;
 
 	return kvm_lapic_msr_write(apic, reg, data);
 }
-- 
2.36.1.124.g0e6072fb45-goog


  reply	other threads:[~2022-05-25 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25 17:39 [PATCH v2 1/2] KVM: Inject #GP on invalid write to APIC_SELF_IPI register Venkatesh Srinivas
2022-05-25 17:39 ` Venkatesh Srinivas [this message]
2022-05-25 18:30   ` [PATCH v2 2/2] KVM: Inject #GP on invalid writes to x2APIC registers Sean Christopherson
2022-05-27  8:15   ` [KVM] 317463a437: kvm-unit-tests.apic-split.fail kernel test robot
2022-05-27  8:15     ` kernel test robot
2022-05-25 18:42 ` [PATCH v2 1/2] KVM: Inject #GP on invalid write to APIC_SELF_IPI register Sean Christopherson
2022-09-14 21:46 ` Jim Mattson

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=20220525173933.1611076-2-venkateshs@chromium.org \
    --to=venkateshs@chromium.org \
    --cc=kvm@vger.kernel.org \
    --cc=marcorr@google.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 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.