From: Lorenzo Stoakes <ljs@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Carlier <devnexen@gmail.com>,
David Hildenbrand <david@kernel.org>,
Heechan Kang <gganji11@naver.com>,
"Liam R. Howlett" <liam@infradead.org>,
Michael Bommarito <michael.bommarito@gmail.com>,
Peter Xu <peterx@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] userfaultfd: verify VMA state across UFFDIO_COPY retry
Date: Mon, 8 Jun 2026 14:03:11 +0100 [thread overview]
Message-ID: <aia8nKXtShnhQpVY@lucifer> (raw)
In-Reply-To: <ahhUM0A8-q0UqFv1@kernel.org>
On Thu, May 28, 2026 at 05:41:55PM +0300, Mike Rapoport wrote:
> On Thu, May 28, 2026 at 02:31:00PM +0100, Lorenzo Stoakes wrote:
> > On Wed, May 27, 2026 at 09:47:49PM +0300, Mike Rapoport wrote:
> > > From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
> > >
> > > mfill_copy_folio_retry() drops the VMA lock for copy_from_user() and
> > > reacquires it afterwards. The destination VMA can be replaced during that
> > > window.
> > >
> > > The existing check compares vma_uffd_ops() before and after the retry, but
> > > if a shmem VMA with MAP_SHARED is replaced with a shmem VMA with
> > > MAP_PRIVATE (or vice versa) the replacement goes undetected.
> > >
> > > The change from MAP_PRIVATE to MAP_SHARED will treat the folio allocated
> > > with shmem_alloc_folio() as anonymous and this will cause BUG() when
> > > mfill_atomic_install_pte() will try to folio_add_new_anon_rmap().
> > >
> > > The change from MAP_SHARED to MAP_PRIVATE allows injection of folios into
> > > the page cache of the original VMA.
> > >
> > > There is no need to change for hugetlb because it never uses
> > > mfill_copy_folio_retry().
> > >
> > > Introduce helpers for more comprehensive comparison of VMA state:
> > > - mfill_retry_state_save() to save the relevant VMA state into a struct
> > > mfill_retry_state (original uffd_ops, relevant VMA flags, vm_file and
> > > pgoff) before dropping the lock
> > > - mfill_retry_state_changed() to compare the saved state with the state
> > > of the VMA acquired after retaking the locks
> > > - mfill_retry_state_put() to release vm_file pinning.
> > >
> > > Use DEFINE_FREE() cleanup to wrap mfill_retry_state_put() to avoid
> > > complicating error handling paths in mfill_copy_folio_retry().
> > >
> > > Fixes: 292411fda25b ("mm/userfaultfd: detect VMA type change after copy retry in mfill_copy_folio_retry()")
> > > Fixes: 6ab703034f14 ("userfaultfd: mfill_atomic(): remove retry logic")
> >
> > Did we want a Cc: Stable?
>
> Andrew adds it when applying.
Hmm, I didn't think this always happened by default? :)
>
> > > Suggested-by: Peter Xu <peterx@redhat.com>
> > > Co-developed-by: David Carlier <devnexen@gmail.com>
> > > Signed-off-by: David Carlier <devnexen@gmail.com>
> > > Co-developed-by: Michael Bommarito <michael.bommarito@gmail.com>
> > > Signed-off-by: Michael Bommarito <michael.bommarito@gmail.com>
> > > Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> >
> > OK the logic here looks good, thanks for the changes. I have one comment below
> > re: a redundant check, with that addressed feel free to add:
> >
> > Reviewed-by: Lorenzo Stoakes <ljs@kernel.org>
> >
> > > ---
> > > mm/userfaultfd.c | 85 +++++++++++++++++++++++++++++++++++++++++-------
> > > 1 file changed, 73 insertions(+), 12 deletions(-)
> >
> > > +static bool mfill_retry_state_changed(struct mfill_retry_state *state,
> > > + struct vm_area_struct *vma)
> > > +{
> > > + vma_flags_t flags = vma_flags_and_mask(&vma->flags,
> > > + MFILL_RETRY_STATE_VMA_FLAGS);
> > > +
> > > + /* Have any UFFD flags (missing, WP, minor) changed? */
> > > + if (!vma_flags_same_pair(&state->flags, &flags))
> > > + return true;
> > > +
> > > + /* VMA type or effective uffd_ops changed while the lock was dropped */
> > > + if (state->ops != vma_uffd_ops(vma))
> > > + return true;
> > > +
> > > + /* VMA was anonymous before; changed only if it no longer is */
> > > + if (!state->file)
> > > + return !vma_is_anonymous(vma);
> > > +
> > > + /* VMA was file backed, but file, inode or offset has changed */
> > > + if (!vma->vm_file || vma->vm_file->f_inode != state->file->f_inode ||
> > > + state->file != vma->vm_file || vma->vm_pgoff != state->pgoff)
> > > + return true;
> >
> > Doesn't state->file != vma->vm_file render the inode check redundant?
>
> Nope, struct file is TYPESAFE_BY_RCU, it can be recycled with the same
> file * pointing to different objects.
Oh lord :)
OK ack on that then!
>
> --
> Sincerely yours,
> Mike.
Cheers, Lorenzo
next prev parent reply other threads:[~2026-06-08 13:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 18:47 [PATCH v2 0/3] " Mike Rapoport
2026-05-27 18:47 ` [PATCH v2 1/3] " Mike Rapoport
2026-05-28 13:31 ` Lorenzo Stoakes
2026-05-28 14:41 ` Mike Rapoport
2026-05-28 21:04 ` Andrew Morton
2026-06-08 13:03 ` Lorenzo Stoakes [this message]
2026-06-08 16:39 ` Andrew Morton
2026-06-08 18:57 ` Mike Rapoport
2026-05-27 18:47 ` [PATCH v2 2/3] userfaultfd: refuse to __mfill_atomic_pte() for unsupported VMAs Mike Rapoport
2026-05-27 19:09 ` David CARLIER
2026-05-28 7:33 ` Mike Rapoport
2026-05-28 7:34 ` David CARLIER
2026-05-28 13:11 ` Lorenzo Stoakes
2026-05-27 18:47 ` [PATCH v2 3/3] userfaultfd: remove redundant check in vm_uffd_ops() Mike Rapoport
2026-05-28 13:10 ` Lorenzo Stoakes
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=aia8nKXtShnhQpVY@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=devnexen@gmail.com \
--cc=gganji11@naver.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=michael.bommarito@gmail.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.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