From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
pbonzini@redhat.com, Yan Zhao <yan.y.zhao@intel.com>
Cc: reinette.chatre@intel.com, rick.p.edgecombe@intel.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH v2 0/3] KVM: Fix deadlock for invalid memslots
Date: Mon, 15 Sep 2025 17:25:49 -0700 [thread overview]
Message-ID: <175798196007.623278.10358907796048599575.b4-ty@google.com> (raw)
In-Reply-To: <20250822070305.26427-1-yan.y.zhao@intel.com>
On Fri, 22 Aug 2025 15:03:04 +0800, Yan Zhao wrote:
> 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.
>
> [...]
Applied 1 and 2 to kvm-x86 mmu. I'll post a proper patch for the selftest once
I figure out what I intended with respect to range.size.
Thanks!
[1/3] KVM: x86/mmu: Return -EAGAIN if userspace deletes/moves memslot during prefault
https://github.com/kvm-x86/linux/commit/3ccbf6f47098
[2/3] KVM: TDX: Do not retry locally when the retry is caused by invalid memslot
https://github.com/kvm-x86/linux/commit/2bc2694fe20b
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2025-09-16 0:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 7:03 Yan Zhao
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 ` Sean Christopherson [this message]
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=175798196007.623278.10358907796048599575.b4-ty@google.com \
--to=seanjc@google.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=yan.y.zhao@intel.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®