mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Michal Luczaj <mhal@rbox.co>, Haoyu Wu <haoyuwu254@gmail.com>,
	 syzbot+545f1326f405db4e1c3e@syzkaller.appspotmail.com
Subject: [PATCH 0/2] KVM: x86: Disallow changing x2APIC ID via userspace
Date: Fri,  2 Aug 2024 13:29:39 -0700	[thread overview]
Message-ID: <20240802202941.344889-1-seanjc@google.com> (raw)

Silently ignore userspace attempts to change the x2APIC ID via
KVM_SET_LAPIC.

I've been hunting for this series since January[*], and *finally* stumbled
across it while tidying up my (too) many git trees.

[*] https://lore.kernel.org/all/ZbPkHvuJv0EdJhVN@google.com

Michal Luczaj (1):
  KVM: selftests: Add a testcase to verify x2APIC is fully readonly

Sean Christopherson (1):
  KVM: x86: Make x2APIC ID 100% readonly

 arch/x86/kvm/lapic.c                          | 18 +++++++++---
 .../selftests/kvm/x86_64/xapic_state_test.c   | 28 +++++++++++++++++++
 2 files changed, 42 insertions(+), 4 deletions(-)


base-commit: 332d2c1d713e232e163386c35a3ba0c1b90df83f
-- 
2.46.0.rc2.264.g509ed76dc8-goog


             reply	other threads:[~2024-08-02 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 20:29 Sean Christopherson [this message]
2024-08-02 20:29 ` [PATCH 1/2] KVM: x86: Make x2APIC ID 100% readonly Sean Christopherson
2024-08-04 20:30   ` Michal Luczaj
2024-08-05 16:26     ` Sean Christopherson
2024-08-13 16:01       ` Paolo Bonzini
2024-08-02 20:29 ` [PATCH 2/2] KVM: selftests: Add a testcase to verify x2APIC is fully readonly Sean Christopherson

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=20240802202941.344889-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=haoyuwu254@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhal@rbox.co \
    --cc=pbonzini@redhat.com \
    --cc=syzbot+545f1326f405db4e1c3e@syzkaller.appspotmail.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®