From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: David Hildenbrand <david@kernel.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Yan Zhao <yan.y.zhao@intel.com>,
Vishal Annapurve <vannapurve@google.com>
Subject: Re: [PATCH v2] KVM: guest_memfd: Elaborate on how release() vs. get_pfn() is safe against UAF
Date: Thu, 24 Sep 2026 14:51:53 -0700 [thread overview]
Message-ID: <179028369147.2007668.960049765709883203.b4-ty@b4> (raw)
In-Reply-To: <20260826165647.769231-1-seanjc@google.com>
On Wed, 26 Aug 2026 09:56:47 -0700, Sean Christopherson wrote:
> Add more context and information to the comment in kvm_gmem_release() that
> explains why there's no synchronization on RCU _or_ kvm->srcu. Point (b)
> from commit 67b43038ce14 ("KVM: guest_memfd: Remove RCU-protected attribute
> from slot->gmem.file")
>
> b) kvm->srcu ensures that kvm_gmem_unbind() and freeing of a memslot
> occur after the memslot is no longer visible to kvm_gmem_get_pfn().
>
> [...]
Applied to kvm-x86 coco. I'll follow-up with another cleanup for get_pfn() at
some point. Thanks!
[1/1] KVM: guest_memfd: Elaborate on how release() vs. get_pfn() is safe against UAF
https://github.com/kvm-x86/linux/commit/53c34396c19e
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2026-09-24 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 16:56 Sean Christopherson
2026-09-20 12:55 ` Yan Zhao
2026-09-21 13:40 ` Sean Christopherson
2026-09-21 13:43 ` Sean Christopherson
2026-09-22 3:47 ` Yan Zhao
2026-09-22 3:45 ` Yan Zhao
2026-09-22 14:22 ` Sean Christopherson
2026-09-23 5:01 ` Yan Zhao
2026-09-24 21:51 ` 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=179028369147.2007668.960049765709883203.b4-ty@b4 \
--to=seanjc@google.com \
--cc=david@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vannapurve@google.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®