From: David Hildenbrand <david@redhat.com>
To: Suren Baghdasaryan <surenb@google.com>, akpm@linux-foundation.org
Cc: peterx@redhat.com, aarcange@redhat.com, lokeshgidra@google.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
syzbot+b446dbe27035ef6bd6c2@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/1] userfaultfd: fix a crash when UFFDIO_MOVE handles a THP hole
Date: Fri, 1 Aug 2025 09:21:30 +0200 [thread overview]
Message-ID: <d2b6be85-44d5-4a87-bfe5-4a9e80f95bb8@redhat.com> (raw)
In-Reply-To: <20250731154442.319568-1-surenb@google.com>
On 31.07.25 17:44, Suren Baghdasaryan wrote:
Hi!
Did you mean in you patch description:
"userfaultfd: fix a crash in UFFDIO_MOVE with some non-present PMDs"
Talking about THP holes is very very confusing.
> When UFFDIO_MOVE is used with UFFDIO_MOVE_MODE_ALLOW_SRC_HOLES and it
> encounters a non-present THP, it fails to properly recognize an unmapped
You mean a "non-present PMD that is not a migration entry".
> hole and tries to access a non-existent folio, resulting in
> a crash. Add a check to skip non-present THPs.
That makes sense. The code we have after this patch is rather
complicated and hard to read.
>
> Fixes: adef440691ba ("userfaultfd: UFFDIO_MOVE uABI")
> Reported-by: syzbot+b446dbe27035ef6bd6c2@syzkaller.appspotmail.com
> Closes: https://lore.kernel.org/all/68794b5c.a70a0220.693ce.0050.GAE@google.com/
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
> Cc: stable@vger.kernel.org
> ---
> Changes since v1 [1]
> - Fixed step size calculation, per Lokesh Gidra
> - Added missing check for UFFDIO_MOVE_MODE_ALLOW_SRC_HOLES, per Lokesh Gidra
>
> [1] https://lore.kernel.org/all/20250730170733.3829267-1-surenb@google.com/
>
> mm/userfaultfd.c | 45 +++++++++++++++++++++++++++++----------------
> 1 file changed, 29 insertions(+), 16 deletions(-)
>
> diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
> index cbed91b09640..b5af31c22731 100644
> --- a/mm/userfaultfd.c
> +++ b/mm/userfaultfd.c
> @@ -1818,28 +1818,41 @@ ssize_t move_pages(struct userfaultfd_ctx *ctx, unsigned long dst_start,
>
> ptl = pmd_trans_huge_lock(src_pmd, src_vma);
> if (ptl) {
> - /* Check if we can move the pmd without splitting it. */
> - if (move_splits_huge_pmd(dst_addr, src_addr, src_start + len) ||
> - !pmd_none(dst_pmdval)) {
> - struct folio *folio = pmd_folio(*src_pmd);
> + if (pmd_present(*src_pmd) || is_pmd_migration_entry(*src_pmd)) {
> + /* Check if we can move the pmd without splitting it. */
> + if (move_splits_huge_pmd(dst_addr, src_addr, src_start + len) ||
> + !pmd_none(dst_pmdval)) {
> + if (pmd_present(*src_pmd)) {
> + struct folio *folio = pmd_folio(*src_pmd);
> +
> + if (!folio || (!is_huge_zero_folio(folio) &&
> + !PageAnonExclusive(&folio->page))) {
> + spin_unlock(ptl);
> + err = -EBUSY;
> + break;
> + }
> + }
... in particular that. Is there some way to make this code simpler /
easier to read? Like moving that whole last folio-check thingy into a
helper?
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-08-01 7:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 15:44 Suren Baghdasaryan
2025-07-31 17:30 ` Lokesh Gidra
2025-08-01 7:21 ` David Hildenbrand [this message]
2025-08-01 14:15 ` Peter Xu
2025-08-01 15:28 ` Suren Baghdasaryan
2025-08-01 16:23 ` Peter Xu
2025-08-01 16:41 ` Suren Baghdasaryan
2025-08-01 17:13 ` Peter Xu
2025-08-01 17:45 ` Suren Baghdasaryan
2025-08-01 18:20 ` Peter Xu
2025-08-01 19:30 ` Suren Baghdasaryan
2025-08-02 0:32 ` Peter Xu
2025-08-04 14:55 ` Suren Baghdasaryan
2025-08-05 14:39 ` Peter Xu
2025-08-05 14:57 ` Suren Baghdasaryan
2025-08-05 20:39 ` Suren Baghdasaryan
2025-08-05 23:41 ` Suren Baghdasaryan
2025-08-06 0:40 ` Peter Xu
2025-08-06 15:06 ` Suren Baghdasaryan
2025-08-06 15:46 ` Suren Baghdasaryan
2025-08-01 15:11 ` Suren Baghdasaryan
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=d2b6be85-44d5-4a87-bfe5-4a9e80f95bb8@redhat.com \
--to=david@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=peterx@redhat.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=syzbot+b446dbe27035ef6bd6c2@syzkaller.appspotmail.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