From: Sean Christopherson <seanjc@google.com>
To: Ackerley Tng <ackerleytng@google.com>
Cc: Alexandru Elisei <alexandru.elisei@arm.com>,
sashiko-reviews@lists.linux.dev, Marc Zyngier <maz@kernel.org>,
kvm@vger.kernel.org, kvmarm@lists.linux.dev,
Oliver Upton <oupton@kernel.org>
Subject: Re: [RFC PATCH] KVM: Ignore MMU notifiers for guest_memfd-only memslots
Date: Wed, 24 Jun 2026 10:32:49 -0700 [thread overview]
Message-ID: <ajwUwX2xIOLjACh0@google.com> (raw)
In-Reply-To: <CAEvNRgE9cLfjDbXuR5wq3fEWZyHxYPxdExxNjXUFO1nT5m==1A@mail.gmail.com>
On Tue, Jun 23, 2026, Ackerley Tng wrote:
> Sean Christopherson <seanjc@google.com> writes:
> > and purposes, we're conceptually treating conversions as free()+re-alloc(). So
> > while the page might still be in the page cache, it's effectively been "freed".
> > So in that case, KVM really does need to ensure it handles mmu_notifier events
> > correctly to avoid UAF.
>
> Just making sure: "handle mmu_notifier events" here refers to
> gfn_to_pfn_cache and other parts of KVM that works with memory.
Yes.
> There's no issue with a UAF between mmu_notifier invalidations and
> conversions, right?
Right.
next prev parent reply other threads:[~2026-06-24 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 15:52 [RFC PATCH] KVM: Ignore MMU notifiers for guest_memfd-only memslots Alexandru Elisei
2026-06-15 16:09 ` sashiko-bot
2026-06-15 17:47 ` Sean Christopherson
2026-06-15 18:09 ` Sean Christopherson
2026-06-18 11:09 ` Alexandru Elisei
2026-06-17 13:07 ` Alexandru Elisei
2026-06-17 21:21 ` Sean Christopherson
2026-06-18 10:19 ` Alexandru Elisei
2026-06-23 23:41 ` Ackerley Tng
2026-06-24 17:32 ` Sean Christopherson [this message]
2026-06-17 21:22 ` Sean Christopherson
2026-06-18 11:26 ` David Hildenbrand (Arm)
2026-06-15 19:07 ` David Hildenbrand
2026-06-17 13:23 ` Alexandru Elisei
2026-06-17 13:41 ` David Hildenbrand
2026-06-17 13:50 ` Alexandru Elisei
2026-06-21 0:02 ` XIAO WU
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=ajwUwX2xIOLjACh0@google.com \
--to=seanjc@google.com \
--cc=ackerleytng@google.com \
--cc=alexandru.elisei@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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