From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: Fixes for 7.3-rcN
Date: Fri, 25 Sep 2026 16:33:21 -0700 [thread overview]
Message-ID: <20260925233321.2381319-1-seanjc@google.com> (raw)
Please pull a variety of fixes. Nothing is super urgent, but all of these can
be fatal to the host and/or guest (except for the selftest change, which fixes
a regression that was introduced in 7.3).
The following changes since commit d599822bdb66aeec5ec76297b0fc6efaaeefe07c:
Merge tag 'kvm-s390-master-7.3-1' of https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into HEAD (2026-09-04 17:34:28 +0200)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-fixes-7.3-rc5
for you to fetch changes up to 119e9db233ad0f4cbd4cfb9f9385a7bca378b37d:
KVM: Don't pre-reserve xarray entries when storing empty/NULL attributes (2026-09-22 08:36:16 -0700)
----------------------------------------------------------------
KVM fixes for 7.3-rcN
- Fix a brown paper bag bug where KVM would incorrectly treat Intel PMU MSRs
as valid on AMD.
- Fix a regression in the hardware disable selftest where it checked the wrong
macro when detecting glibc support (breaks at least musl).
- Never clear KVM_REQ_VM_DEAD so that dead VMs stay dead, which is especially
important for KVM_BUG_ON() flows, which often guard more dangerous bugs.
- Re-pend GET_NESTED_STATE_PAGES if getting the pages fails, to fix a bug
where KVM would let userspace run a broken setup with stale vmcs12 pages.
- Fix a class of bugs where KVM would fail to fill kvm_run exit fields if
getting nested pages failed.
- Treat reserved entries in the memory attributes xarray as "no attributes",
to fix false positives when checking for mixed attributes.
- Fix memcg accounting for the memory attributes xarray (the xarray library
subtly requires the xarray to be configured for accounting upfront; the gfp
flags taken at runtime are used only rarely).
- Don't pre-reserve xarray entries when storing empty attributes, as storing
NULL must not require memory allocation (KVM and other subsystems heavily
rely on this behavior).
----------------------------------------------------------------
David Ballesteros (1):
KVM: Ensure memory attributes xarray nodes are accounted to the caller's memcg
Jim Mattson (1):
KVM: x86/pmu: Move Intel PMU global MSRs to intel_is_valid_msr()
Sean Christopherson (4):
KVM: selftests: Use __GLIBC__, not _GNU_SOURCE, to detect actual glibc
KVM: Never clear KVM_REQ_VM_DEAD from a vCPU's requests
KVM: x86: Re-pend GET_NESTED_STATE_PAGES if getting said pages fails
KVM: x86: Fill kvm_run exit fields in common get_nested_state_pages() error paths
Zeng Chi (2):
KVM: Don't treat reserved xarray entries as having memory attributes
KVM: Don't pre-reserve xarray entries when storing empty/NULL attributes
arch/arm64/kvm/arm.c | 2 +-
arch/x86/kvm/mmu/mmu.c | 2 +-
arch/x86/kvm/pmu.c | 8 -----
arch/x86/kvm/svm/nested.c | 7 +----
arch/x86/kvm/vmx/nested.c | 15 ++++------
arch/x86/kvm/vmx/pmu_intel.c | 3 ++
arch/x86/kvm/vmx/tdx.c | 2 +-
arch/x86/kvm/x86.c | 6 +++-
include/linux/kvm_host.h | 9 ++++--
.../testing/selftests/kvm/hardware_disable_test.c | 6 ++--
virt/kvm/kvm_main.c | 35 ++++++++++++++++++----
11 files changed, 56 insertions(+), 39 deletions(-)
next reply other threads:[~2026-09-25 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 23:33 Sean Christopherson [this message]
2026-09-26 4:40 ` Paolo Bonzini
2026-09-28 15:41 ` Sean Christopherson
2026-09-28 15:56 ` 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=20260925233321.2381319-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®