From: Yan Zhao <yan.y.zhao@intel.com>
To: pbonzini@redhat.com, seanjc@google.com
Cc: reinette.chatre@intel.com, rick.p.edgecombe@intel.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Yan Zhao <yan.y.zhao@intel.com>
Subject: [PATCH v2 0/3] KVM: Fix deadlock for invalid memslots
Date: Fri, 22 Aug 2025 15:03:04 +0800 [thread overview]
Message-ID: <20250822070305.26427-1-yan.y.zhao@intel.com> (raw)
Hi,
This series addresses the deadlock issue encountered with invalid memslots
during prefaulting or TDX private EPT violations.
Patches 1-2 are the new fixes from Sean.
Patch 1 is for the prefaulting case,
patch 2 for the TDX private EPT violation case.
Patch 3 updates the selftest for prefaulting.
The ioctl KVM_PRE_FAULT_MEMORY is now expected to return EAGAIN
instead of ENOENT when prefaulting GFNs in an invalid memslot.
The TDX-specific selftest is not included in this series, though it's
passed locally.
v2:
- Use Sean suggested fixes (patches 1-2).
- Updated selftest for the prefault case accordingly.
- code base: kvm-x86-next-2025.08.21
v1:
https://lore.kernel.org/all/20250519023613.30329-1-yan.y.zhao@intel.com
Sean Christopherson (2):
KVM: x86/mmu: Return -EAGAIN if userspace deletes/moves memslot during
prefault
KVM: TDX: Do not retry locally when the retry is caused by invalid
memslot
Yan Zhao (1):
KVM: selftests: Test prefault memory during concurrent memslot removal
arch/x86/kvm/mmu/mmu.c | 10 +-
arch/x86/kvm/vmx/tdx.c | 11 +++
.../selftests/kvm/pre_fault_memory_test.c | 94 +++++++++++++++----
virt/kvm/kvm_main.c | 1 +
4 files changed, 98 insertions(+), 18 deletions(-)
--
2.43.2
next reply other threads:[~2025-08-22 7:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 7:03 Yan Zhao [this message]
2025-08-22 7:03 ` [PATCH v2 1/3] KVM: x86/mmu: Return -EAGAIN if userspace deletes/moves memslot during prefault Yan Zhao
2025-09-09 2:46 ` Binbin Wu
2025-08-22 7:05 ` [PATCH v2 2/3] KVM: TDX: Do not retry locally when the retry is caused by invalid memslot Yan Zhao
2025-09-09 3:29 ` Binbin Wu
2025-09-09 14:18 ` Sean Christopherson
2025-09-10 2:02 ` Binbin Wu
2025-08-22 7:05 ` [PATCH v2 3/3] KVM: selftests: Test prefault memory during concurrent memslot removal Yan Zhao
2025-09-08 23:47 ` Sean Christopherson
2025-09-15 8:21 ` Yan Zhao
2025-09-16 0:14 ` Sean Christopherson
2025-09-24 17:09 ` Sean Christopherson
2025-09-16 0:25 ` [PATCH v2 0/3] KVM: Fix deadlock for invalid memslots 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=20250822070305.26427-1-yan.y.zhao@intel.com \
--to=yan.y.zhao@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.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®