From: Suren Baghdasaryan <surenb@google.com>
To: Peter Xu <peterx@redhat.com>
Cc: David Hildenbrand <david@redhat.com>,
akpm@linux-foundation.org, 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: Wed, 6 Aug 2025 08:06:04 -0700 [thread overview]
Message-ID: <CAJuCfpGpEOaKdqpqTpfbw1cdHEEWhiu6KRFQFWaM-AKODiDFcg@mail.gmail.com> (raw)
In-Reply-To: <aJKkjEYmeq93w35-@x1.local>
On Tue, Aug 5, 2025 at 5:41 PM Peter Xu <peterx@redhat.com> wrote:
>
> On Tue, Aug 05, 2025 at 04:41:18PM -0700, Suren Baghdasaryan wrote:
> > Ok, I let the reproducer run for half a day and it did not hit this
> > case, so I must have done something wrong during my initial
> > investigation. Sorry for the confusion. I could have sworn that I saw
> > this case but now it just does not happen.
>
> I'm wildly guessing you might have hit the numa balancing bug I mentioned,
> that might explain what you mentioned previously on the testing results.
> It might just be tricky to reproduce:
>
> - We'll need a valid THP (pmd) first in the MOVE source region
>
> - THP needs to be selected by numa balancing for a check (marking
> prot_none)
>
> - (before any further access..) UFFDIO_MOVE needs to happen on top trying
> to move the whole THP being marked as prot_none.
>
> AFAICT, task_numa_work() is the only place that can mark the THP, and when
> it happens, should see change_huge_pmd(cp_flags=MM_CP_PROT_NUMA) and then
> returns with HPAGE_PMD_NR.
>
> [sorry I am still pretty occupied with other things. I can try to reproduce
> together with you after I get more time back]
>
> > With migration entry being the only case that leads to that
> > pmd_folio(), the only check we need to add is the "if
> > (pmd_present(*src_pmd))" before pmd_folio(). Would you like me to
> > check anything else or should I go ahead and post that fix?
>
> We could fix the migration entry first, then if any of us can reproduce the
> above numa balancing issue then it can be a 2nd patch on top.
>
> After all, so far we didn't yet prove it, either some unreproduceable test,
> or pure code analysis. Meanwhile it might also be cleaner if we have one
> patch fix one issue, rather than having one patch fix two bugs.
>
> What do you think?
Agree, that seems reasonable. I'll post the new fix today.
Thanks,
Suren.
>
> Thanks,
>
> --
> Peter Xu
>
next prev parent reply other threads:[~2025-08-06 15:06 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
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 [this message]
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=CAJuCfpGpEOaKdqpqTpfbw1cdHEEWhiu6KRFQFWaM-AKODiDFcg@mail.gmail.com \
--to=surenb@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--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=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