Received-SPF: pass (google.com: domain of linux-kernel+bounces-97659-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Reply-To: Sean Christopherson <seanjc@google.com>
Date: Fri,  8 Mar 2024 14:36:55 -0800
In-Reply-To: <20240308223702.1350851-1-seanjc@google.com>
Precedence: bulk
Mime-Version: 1.0
References: <20240308223702.1350851-1-seanjc@google.com>
Message-ID: <20240308223702.1350851-3-seanjc@google.com>
Subject: [GIT PULL] KVM: Common MMU changes for 6.9
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>
Content-Type: text/plain; charset="UTF-8"

Two small cleanups in what is effectively common MMU code.

The following changes since commit 41bccc98fb7931d63d03f326a746ac4d429c1dd3:

  Linux 6.8-rc2 (2024-01-28 17:01:12 -0800)

are available in the Git repository at:

  https://github.com/kvm-x86/linux.git tags/kvm-x86-generic-6.9

for you to fetch changes up to ea3689d9df50c283cb5d647a74aa45e2cc3f8064:

  KVM: fix kvm_mmu_memory_cache allocation warning (2024-02-22 17:02:26 -0800)

----------------------------------------------------------------
KVM common MMU changes for 6.9:

  - Harden KVM against underflowing the active mmu_notifier invalidation
    count, so that "bad" invalidations (usually due to bugs elsehwere in the
    kernel) are detected earlier and are less likely to hang the kernel.

  - Fix a benign bug in __kvm_mmu_topup_memory_cache() where the object size
    and number of objects parameters to kvmalloc_array() were swapped.

----------------------------------------------------------------
Arnd Bergmann (1):
      KVM: fix kvm_mmu_memory_cache allocation warning

Sean Christopherson (1):
      KVM: Harden against unpaired kvm_mmu_notifier_invalidate_range_end() calls

 virt/kvm/kvm_main.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)