From: Mike Rapoport <rppt@kernel.org>
To: Usama Arif <usama.arif@linux.dev>
Cc: David Carlier <devnexen@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Xu <peterx@redhat.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <ljs@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>, Jann Horn <jannh@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] mm/userfaultfd: detect VMA type change after copy retry in mfill_copy_folio_retry()
Date: Sun, 12 Apr 2026 18:36:40 +0300 [thread overview]
Message-ID: <adu8CNz2USFyL2nN@kernel.org> (raw)
In-Reply-To: <20260410114809.3592720-1-usama.arif@linux.dev>
Hi Usama,
On Fri, Apr 10, 2026 at 04:48:08AM -0700, Usama Arif wrote:
> On Thu, 9 Apr 2026 13:06:53 +0100 David Carlier <devnexen@gmail.com> wrote:
>
> > mfill_copy_folio_retry() drops mmap_lock for the copy_from_user() call.
> > During this window, the VMA can be replaced with a different type (e.g.
> > hugetlb), making the caller's ops pointer stale. Subsequent use of the
> > stale ops can lead to incorrect folio handling or a kernel crash.
> >
> > Pass the caller's ops into mfill_copy_folio_retry() and compare against
> > the current vma_uffd_ops() after re-acquiring the lock. Return -EAGAIN
> > if they differ so the operation can be retried.
> >
> > Fixes: 59da5c32ffa3 ("userfaultfd: mfill_atomic(): remove retry logic")
> > Signed-off-by: David Carlier <devnexen@gmail.com>
> > ---
> > mm/userfaultfd.c | 14 ++++++++++++--
> > 1 file changed, 12 insertions(+), 2 deletions(-)
> >
> > diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
> > index 481ec7eb4442..214923a411c1 100644
> > --- a/mm/userfaultfd.c
> > +++ b/mm/userfaultfd.c
> > @@ -443,7 +443,9 @@ static int mfill_copy_folio_locked(struct folio *folio, unsigned long src_addr)
> > return ret;
> > }
> >
> > -static int mfill_copy_folio_retry(struct mfill_state *state, struct folio *folio)
> > +static int mfill_copy_folio_retry(struct mfill_state *state,
> > + const struct vm_uffd_ops *ops,
> > + struct folio *folio)
> > {
> > unsigned long src_addr = state->src_addr;
> > void *kaddr;
> > @@ -465,6 +467,14 @@ static int mfill_copy_folio_retry(struct mfill_state *state, struct folio *folio
> > if (err)
> > return err;
> >
> > + /*
> > + * The VMA type may have changed while the lock was dropped
> > + * (e.g. replaced with a hugetlb mapping), making the caller's
> > + * ops pointer stale.
> > + */
> > + if (vma_uffd_ops(state->vma) != ops)
> > + return -EAGAIN;
> > +
>
> hmm I am not sure if this is correct for shmem MAP_PRIVATE.
>
> mfill_atomic_pte_copy() overrides ops to &anon_uffd_ops for MAP_PRIVATE
> mappings:
>
> if (!(state->vma->vm_flags & VM_SHARED))
> ops = &anon_uffd_ops;
>
> This overridden ops pointer propagates through __mfill_atomic_pte() into
> mfill_copy_folio_retry(). But the new check here calls vma_uffd_ops()
> which returns the original file-backed ops (e.g. &shmem_uffd_ops).
> For shmem MAP_PRIVATE VMAs, the comparison always fails even when
> the VMA type has not changed.
Good catch.
@Andrew, can you please drop the patch for now?
> Maybe save the original (non-overridden) ops before the MAP_PRIVATE override
> and compare against that?
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-04-12 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 12:06 [PATCH v5] mm/userfaultfd: detect VMA type change after copy retry in mfill_copy_folio_retry() David Carlier
2026-04-09 15:20 ` Mike Rapoport
2026-04-09 17:04 ` Vlastimil Babka (SUSE)
2026-04-09 17:14 ` Andrew Morton
2026-04-09 17:09 ` Peter Xu
2026-04-09 18:12 ` Mike Rapoport
2026-04-10 11:48 ` Usama Arif
2026-04-12 15:36 ` Mike Rapoport [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=adu8CNz2USFyL2nN@kernel.org \
--to=rppt@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=devnexen@gmail.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=peterx@redhat.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@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