Re: [PATCH] fork: mark memcpy() in dup_mm() with data_race()

From: Lorenzo Stoakes (ARM)

Date: Tue Nov 17 2026 - 07:59:07 EST


On Tue, Nov 17, 2026 at 10:59:56AM +0500, Muhammad Haris Awan wrote:
> KCSAN reported a data race between dup_mm() copying oldmm via
> memcpy(mm, oldmm, sizeof(*mm)) and lru_gen_del_mm() modifying
> oldmm->lru_gen.list when an adjacent mm_struct on the shared
> mm_list->fifo is removed under mm_list->lock.
>
> oldmm->lru_gen and oldmm->mmlist are protected by mm_list->lock /
> mmlist_lock (or updated locklessly via lru_gen_use_mm()), not
> oldmm->mmap_lock. Because struct mm_struct uses __randomize_layout and

Firstly what on earth does __randomize_layout have to do with anything?

Secondly, ef694e2d2101 takes the oldmm mmap_lock so what you're saying here is
wrong.

The problem is that you end up manipulating a neighbouring mm in the list.

> mm_init() immediately reinitializes these fields on the new mm, wrap
> the memcpy() in data_race(), matching dup_vma() in mm/vma_init.c.
>
> Fixes: bd74fdaea146 ("mm: multi-gen LRU: support page table walks")
> Reported-by: syzbot+c6e1b1b32ff2fc3b7d60@xxxxxxxxxxxxxxxxxxxxxxxxx
> Closes: https://syzkaller.appspot.com/bug?extid=c6e1b1b32ff2fc3b7d60
> Signed-off-by: Muhammad Haris Awan <m.harisawan@xxxxxxxxxx>

Given you're a complete newcomer to mm I do have to ask if you used an LLM, you
should mention that somewhere in the commit message or at least below the '---'
by convention.

And it's vital that you understand everything you submit as per
https://docs.kernel.org/process/generated-content.html

So what work are you doing with regard to KCSAN, data races and mm lifetime that
led you to this? And what expertise are you coming to it with?

> ---
> kernel/fork.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/fork.c b/kernel/fork.c
> index 5efceb8d5..14ac9a070 100644
> --- a/kernel/fork.c
> +++ b/kernel/fork.c
> @@ -1539,7 +1539,12 @@ static struct mm_struct *dup_mm(struct task_struct *tsk,
> goto fail_uprobe;
> }
>
> - memcpy(mm, oldmm, sizeof(*mm));
> + /*
> + * oldmm->lru_gen and oldmm->mmlist may be modified concurrently under
> + * mm_list->lock / mmlist_lock or locklessly via lru_gen_use_mm(),
> + * and mm_init() will immediately reinitialize them.
> + */

I really don't like this comment that is begging to bit rot.

> + data_race(memcpy(mm, oldmm, sizeof(*mm)));

That's _really_ horrible.

That's now making it so any race that matters is ignored in a _super_ sensitive
part of mm, because MGLRU decided it was a special snowflake.

But I'm confused as to why in 4 years nobody reported a KCSAN issue with this?
Surely something increased the likelihood of this race?

In any case, this is MGLRU's fault. It's abusing the mm data structure and doing
something it shouldn't.

So any fix should be there. Similarly for other mmlist users.

Or really, given this seems to be a one-off, spurious, KCSAN report, do nothing
until it becomes clear this will be reported more than once in 4 years? :)

>
> if (!mm_init(mm, tsk)) {
> mmap_write_unlock(oldmm);
> --
> 2.56.0
>

--
Cheers, Lorenzo