From: Andrew Morton <akpm@linux-foundation.org>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: Marco Elver <elver@google.com>,
syzbot <syzbot+38a879f4a73497f2dfef@syzkaller.appspotmail.com>,
jannh@google.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ljs@kernel.org, pfalcato@suse.de,
syzkaller-bugs@googlegroups.com, vbabka@kernel.org
Subject: Re: [syzbot] [mm?] KCSAN: data-race in mas_wr_store_entry / mtree_range_walk (2)
Date: Thu, 23 Apr 2026 09:34:20 -0700 [thread overview]
Message-ID: <20260423093420.038ce8c6ffb45279d0a809a0@linux-foundation.org> (raw)
In-Reply-To: <4ub4x275tpkop5jbx3l7p7zqeww32tb2yzhdgqqkvakri7dyih@bdxuedw5utlc>
On Mon, 20 Apr 2026 15:29:00 -0400 "Liam R. Howlett" <Liam.Howlett@oracle.com> wrote:
> Link: https://lkml.kernel.org/r/20230628073657.75314-5-zhangpeng.00@bytedance.com
> Signed-off-by: Peng Zhang <zhangpeng.00@bytedance.com>
> Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>
> So, you can see that the author of the initial code did look at race
> conditions. I wanted to read the link for more information but that
> link isn't working right now (403 error).
lkml links are temporarily broken.
Replacing "lkml.kernekl.org/r" with "lore.kernel.org" fixes it.
https://lore.kernel.org/all/20230628073657.75314-5-zhangpeng.00@bytedance.com/
next prev parent reply other threads:[~2026-04-23 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 9:12 [syzbot] [mm?] KCSAN: data-race in mas_wr_store_entry / mtree_range_walk (2) syzbot
2026-04-17 23:50 ` Liam R. Howlett
2026-04-18 0:25 ` Marco Elver
2026-04-20 19:29 ` Liam R. Howlett
2026-04-23 16:34 ` Andrew Morton [this message]
2026-04-20 8:36 ` Vlastimil Babka (SUSE)
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=20260423093420.038ce8c6ffb45279d0a809a0@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=elver@google.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=pfalcato@suse.de \
--cc=syzbot+38a879f4a73497f2dfef@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@kernel.org \
/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