public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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: vcpu_array fixes and cleanups for 6.14
Date: Thu, 16 Jan 2025 17:07:17 -0800	[thread overview]
Message-ID: <20250117010718.2328467-7-seanjc@google.com> (raw)
In-Reply-To: <20250117010718.2328467-1-seanjc@google.com>

The wonderful vcpu_array changes that you already know and love :-D

The following changes since commit 3522c419758ee8dca5a0e8753ee0070a22157bc1:

  Merge tag 'kvm-riscv-fixes-6.13-1' of https://github.com/kvm-riscv/linux into HEAD (2024-12-13 13:59:20 -0500)

are available in the Git repository at:

  https://github.com/kvm-x86/linux.git tags/kvm-x86-vcpu_array-6.14

for you to fetch changes up to 01528db67f28d5919f7b0a68900dc212165218e2:

  KVM: Drop hack that "manually" informs lockdep of kvm->lock vs. vcpu->mutex (2024-12-16 14:37:30 -0800)

----------------------------------------------------------------
KVM vcpu_array fixes and cleanups for 6.14:

 - Explicitly verify the target vCPU is online in kvm_get_vcpu() to fix a bug
   where KVM would return a pointer to a vCPU prior to it being fully online,
   and give kvm_for_each_vcpu() similar treatment to fix a similar flaw.

 - Wait for a vCPU to come online prior to executing a vCPU ioctl to fix a
   bug where userspace could coerce KVM into handling the ioctl on a vCPU that
   isn't yet onlined.

 - Gracefully handle xa_insert() failures even though such failuires should be
   impossible in practice.

----------------------------------------------------------------
Sean Christopherson (6):
      KVM: Explicitly verify target vCPU is online in kvm_get_vcpu()
      KVM: Verify there's at least one online vCPU when iterating over all vCPUs
      KVM: Grab vcpu->mutex across installing the vCPU's fd and bumping online_vcpus
      Revert "KVM: Fix vcpu_array[0] races"
      KVM: Don't BUG() the kernel if xa_insert() fails with -EBUSY
      KVM: Drop hack that "manually" informs lockdep of kvm->lock vs. vcpu->mutex

 include/linux/kvm_host.h | 16 +++++++++---
 virt/kvm/kvm_main.c      | 68 ++++++++++++++++++++++++++++++++++++------------
 2 files changed, 65 insertions(+), 19 deletions(-)

  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 ` [GIT PULL] KVM: Memslots hardening/cleanups " Sean Christopherson
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 ` Sean Christopherson [this message]
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-7-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