From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: David Carlier <devnexen@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>, Peter Xu <peterx@redhat.com>
Cc: "Liam R . Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <ljs@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: Thu, 9 Apr 2026 19:04:49 +0200 [thread overview]
Message-ID: <b8b1fa91-b3f9-404d-b6b8-f1cb2077a108@kernel.org> (raw)
In-Reply-To: <20260409120653.290386-1-devnexen@gmail.com>
On 4/9/26 14:06, David Carlier 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")
I don't have such sha1, is it a stale mm-unstable commit? Seems to be
4974a6aaa768 ("userfaultfd: mfill_atomic(): remove retry logic") now in
mm-unstable (and can further change)
> 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;
> +
> err = mfill_establish_pmd(state);
> if (err)
> return err;
> @@ -495,7 +505,7 @@ static int __mfill_atomic_pte(struct mfill_state *state,
> * will take care of unlocking if needed.
> */
> if (unlikely(ret)) {
> - ret = mfill_copy_folio_retry(state, folio);
> + ret = mfill_copy_folio_retry(state, ops, folio);
> if (ret)
> goto err_folio_put;
> }
next prev parent reply other threads:[~2026-04-09 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 12:06 David Carlier
2026-04-09 15:20 ` Mike Rapoport
2026-04-09 17:04 ` Vlastimil Babka (SUSE) [this message]
2026-04-09 17:14 ` Andrew Morton
2026-04-09 17:09 ` Peter Xu
2026-04-09 18:12 ` Mike Rapoport
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=b8b1fa91-b3f9-404d-b6b8-f1cb2077a108@kernel.org \
--to=vbabka@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=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