From: Eric Dumazet <edumazet@google.com>
To: Jeongjun Park <aha310510@gmail.com>
Cc: akpm@linux-foundation.org, urezki@gmail.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmalloc: fix data race in show_numa_info()
Date: Mon, 5 May 2025 11:06:22 -0700 [thread overview]
Message-ID: <CANn89i+XaOxe+AOma=H+JuDuFm9b2_1x3x6r6BdhkHFxXAn8Hw@mail.gmail.com> (raw)
In-Reply-To: <20250505171948.24410-1-aha310510@gmail.com>
On Mon, May 5, 2025 at 10:20 AM Jeongjun Park <aha310510@gmail.com> wrote:
>
> The following data-race was found in show_numa_info():
>
> ==================================================================
> BUG: KCSAN: data-race in vmalloc_info_show / vmalloc_info_show
>
> r
> value changed: 0x0000008f -> 0x00000000
>
> Reported by Kernel Concurrency Sanitizer on:
> CPU: 1 UID: 0 PID: 8287 Comm: syz.0.411 Not tainted 6.15.0-rc4-00256-g95d3481af6dc-dirty #1 PREEMPT(voluntary)
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
> ==================================================================
>
> There is a read/write data-race in counter[]. This seems to be happening
> because only read memory barriers are currently applied, so we need to
> modify the write operation to counters[] to be handled atomically.
>
> Fixes: a47a126ad5ea ("vmallocinfo: add NUMA information")
> Signed-off-by: Jeongjun Park <aha310510@gmail.com>
> ---
> mm/vmalloc.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 3ed720a787ec..d93fa535bc21 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -4917,7 +4917,8 @@ bool vmalloc_dump_obj(void *object)
> static void show_numa_info(struct seq_file *m, struct vm_struct *v)
> {
> if (IS_ENABLED(CONFIG_NUMA)) {
> - unsigned int nr, *counters = m->private;
> + atomic_t *counters = m->private;
> + unsigned int nr;
> unsigned int step = 1U << vm_area_page_order(v);
>
> if (!counters)
> @@ -4931,10 +4932,10 @@ static void show_numa_info(struct seq_file *m, struct vm_struct *v)
> memset(counters, 0, nr_node_ids * sizeof(unsigned int));
>
> for (nr = 0; nr < v->nr_pages; nr += step)
> - counters[page_to_nid(v->pages[nr])] += step;
> + atomic_add(step, &counters[page_to_nid(v->pages[nr])]);
> for_each_node_state(nr, N_HIGH_MEMORY)
> - if (counters[nr])
> - seq_printf(m, " N%u=%u", nr, counters[nr]);
> + if (atomic_read(&counters[nr]))
> + seq_printf(m, " N%u=%u", nr, atomic_read(&counters[nr]));
> }
> }
>
> --
This patch looks bogus to me.
The race is about using m->private for storage, while the same file
can be read from multiple threads.
Using atomic_t is going to silence syzbot, but the bug is still there.
next prev parent reply other threads:[~2025-05-05 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 17:19 Jeongjun Park
2025-05-05 18:06 ` Eric Dumazet [this message]
2025-05-05 20:09 ` Eric Dumazet
2025-05-06 5:44 ` Jeongjun Park
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='CANn89i+XaOxe+AOma=H+JuDuFm9b2_1x3x6r6BdhkHFxXAn8Hw@mail.gmail.com' \
--to=edumazet@google.com \
--cc=aha310510@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=urezki@gmail.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