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: Memslots hardening/cleanups for 6.14
Date: Thu, 16 Jan 2025 17:07:12 -0800 [thread overview]
Message-ID: <20250117010718.2328467-2-seanjc@google.com> (raw)
In-Reply-To: <20250117010718.2328467-1-seanjc@google.com>
Please pull a small series to clean up and harden kvm_set_memory_region().
KVM s390 is building on this branch/tag to create a KVM-internal memslot for
its ucontrol stuff, hence the dedicated pull request (and I didn't have any
other pending "generic" changes).
https://lore.kernel.org/all/20250116113355.32184-1-imbrenda@linux.ibm.com
The following changes since commit 10b2c8a67c4b8ec15f9d07d177f63b563418e948:
Merge tag 'kvm-x86-fixes-6.13-rcN' of https://github.com/kvm-x86/linux into HEAD (2024-12-22 12:59:33 -0500)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-memslots-6.14
for you to fetch changes up to 0cc3cb2151f9830274e7bef39a23dc1da1ecd34a:
KVM: Disallow all flags for KVM-internal memslots (2025-01-14 17:36:16 -0800)
----------------------------------------------------------------
KVM kvm_set_memory_region() cleanups and hardening for 6.14:
- Add proper lockdep assertions when setting memory regions.
- Add a dedicated API for setting KVM-internal memory regions.
- Explicitly disallow all flags for KVM-internal memory regions.
----------------------------------------------------------------
Sean Christopherson (5):
KVM: Open code kvm_set_memory_region() into its sole caller (ioctl() API)
KVM: Assert slots_lock is held when setting memory regions
KVM: Add a dedicated API for setting KVM-internal memslots
KVM: x86: Drop double-underscores from __kvm_set_memory_region()
KVM: Disallow all flags for KVM-internal memslots
arch/x86/kvm/x86.c | 7 ++++---
include/linux/kvm_host.h | 8 +++-----
virt/kvm/kvm_main.c | 33 ++++++++++++++-------------------
3 files changed, 21 insertions(+), 27 deletions(-)
next prev parent reply other threads:[~2025-01-17 1:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 1:07 [GIT PULL] KVM x86 pull requests for 6.14 Sean Christopherson
2025-01-17 1:07 ` Sean Christopherson [this message]
2025-01-17 1:07 ` [GIT PULL] KVM: x86: Misc/main changes 6.14 Sean Christopherson
2025-01-17 1:07 ` [GIT PULL] KVM: x86: MMU changes for 6.15 Sean Christopherson
2025-01-17 1:07 ` [GIT PULL] KVM: Selftests changes for 6.14 Sean Christopherson
2025-01-20 11:45 ` Paolo Bonzini
2025-01-21 15:45 ` Sean Christopherson
2025-01-17 1:07 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2025-01-17 1:07 ` [GIT PULL] KVM: vcpu_array fixes and cleanups " Sean Christopherson
2025-01-17 1:07 ` [GIT PULL] KVM: x86: VMX change " 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=20250117010718.2328467-2-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