From: Paolo Bonzini <pbonzini@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [GIT PULL] More KVM fixes for Linux 7.3-rc8 or final
Date: Thu, 15 Oct 2026 11:51:54 +0200 [thread overview]
Message-ID: <20261015095154.815793-1-pbonzini@redhat.com> (raw)
Linus,
The following changes since commit 4056b3c9d3c92ea45955641dbafeb9b960e146ef:
Merge tag 'nios2_update_for_v7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux (2026-10-13 18:06:58 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to c8f4cfe1cf93bce924e27f2abead7a4c4a487505:
KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for !VM-Entry (2026-10-14 16:42:40 +0200)
----------------------------------------------------------------
Even more x86 fixes:
- Avoid a false positive panic in the #PF handler, if the kernel triggers
a page fault within the asynchronous page fault handler before the flags
are reset. This can happen for example because of a perf NMI.
- Always reset a vCPU's MMU pointer back to the root MMU when loading
nested guest state fails during RSM or KVM_SET_NESTED_STATE. Otherwise,
KVM tries to run a non-nested guest with a nested MMU, which can result
in a NULL pointer dereference attempting to get the nested MMU's pgd
(EPTP or nested CR3).
----------------------------------------------------------------
Amirmohammad Eftekhar (1):
KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for !VM-Entry
EJ Campbell (1):
x86/kvm: Don't consume async #PF flags on a kernel #PF in NMI context
arch/x86/kernel/kvm.c | 32 +++++++++++++++++++++++++++++---
arch/x86/kvm/vmx/nested.c | 4 +++-
2 files changed, 32 insertions(+), 4 deletions(-)
next reply other threads:[~2026-10-15 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 9:51 Paolo Bonzini [this message]
2026-10-15 15:17 ` pr-tracker-bot
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=20261015095154.815793-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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®