From: Jeongjun Park <aha310510@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, urezki@gmail.com,
akpm@linux-foundation.org, edumazet@google.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.15.y] mm/vmalloc: fix data race in show_numa_info()
Date: Thu, 3 Jul 2025 21:49:19 +0900 [thread overview]
Message-ID: <CAO9qdTE0SGJTgzTRnOU=tn+uR3kH_zsuuMWEz=0h1k1ottzPWA@mail.gmail.com> (raw)
In-Reply-To: <2025070322-front-purchase-b66f@gregkh>
Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Thu, Jul 03, 2025 at 12:33:12AM +0900, Jeongjun Park wrote:
> > commit 5c5f0468d172ddec2e333d738d2a1f85402cf0bc upstream.
> >
> > The following data-race was found in show_numa_info():
> >
> > ==================================================================
> > BUG: KCSAN: data-race in vmalloc_info_show / vmalloc_info_show
> >
> > read to 0xffff88800971fe30 of 4 bytes by task 8289 on cpu 0:
> > show_numa_info mm/vmalloc.c:4936 [inline]
> > vmalloc_info_show+0x5a8/0x7e0 mm/vmalloc.c:5016
> > seq_read_iter+0x373/0xb40 fs/seq_file.c:230
> > proc_reg_read_iter+0x11e/0x170 fs/proc/inode.c:299
> > ....
> >
> > write to 0xffff88800971fe30 of 4 bytes by task 8287 on cpu 1:
> > show_numa_info mm/vmalloc.c:4934 [inline]
> > vmalloc_info_show+0x38f/0x7e0 mm/vmalloc.c:5016
> > seq_read_iter+0x373/0xb40 fs/seq_file.c:230
> > proc_reg_read_iter+0x11e/0x170 fs/proc/inode.c:299
> > ....
> >
> > value changed: 0x0000008f -> 0x00000000
> > ==================================================================
> >
> > According to this report,there is a read/write data-race because
> > m->private is accessible to multiple CPUs. To fix this, instead of
> > allocating the heap in proc_vmalloc_init() and passing the heap address to
> > m->private, vmalloc_info_show() should allocate the heap.
> >
> > Link: https://lkml.kernel.org/r/20250508165620.15321-1-aha310510@gmail.com
> > Fixes: 8e1d743 ("mm: vmalloc: support multiple nodes in vmallocinfo")
>
> Why did you change this line?
Oops, I accidentally imported the commit message from GitHub, so this
commit hash was shortened to 7 digits. I'll fix it right away and send
v2 patch.
>
> > Signed-off-by: Jeongjun Park <aha310510@gmail.com>
> > Suggested-by: Eric Dumazet <edumazet@google.com>
> > Suggested-by: Andrew Morton <akpm@linux-foundation.org>
> > Reviewed-by: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > ---
> > mm/vmalloc.c | 63 +++++++++++++++++++++++++++++-----------------------
> > 1 file changed, 35 insertions(+), 28 deletions(-)
>
> Please document what you changed from the original version, as this does
> not match what is in Linus's tree.
>
> thanks,
>
> greg k-h
Regards,
Jeongjun Park
prev parent reply other threads:[~2025-07-03 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 15:33 Jeongjun Park
2025-07-03 10:06 ` Greg KH
2025-07-03 12:49 ` Jeongjun Park [this message]
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='CAO9qdTE0SGJTgzTRnOU=tn+uR3kH_zsuuMWEz=0h1k1ottzPWA@mail.gmail.com' \
--to=aha310510@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.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