From: Christian Brauner <brauner@kernel.org>
To: Jianzhou Zhao <luckd0g@163.com>
Cc: linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
jack@suse.cz, linux-fsdevel@vger.kernel.org
Subject: Re: KCSAN: data-race in __d_drop / retain_dentry
Date: Wed, 11 Mar 2026 11:38:03 +0100 [thread overview]
Message-ID: <20260311-stuben-planbar-ab06185adeaa@brauner> (raw)
In-Reply-To: <49420d2.6c84.19cdbeb5e21.Coremail.luckd0g@163.com> <2b8b707a.6a35.19cdbe4c889.Coremail.luckd0g@163.com> <7852a82.6830.19cdbdeea92.Coremail.luckd0g@163.com> <61ff6def.2d0d.19cdad1307e.Coremail.luckd0g@163.com>
On Wed, Mar 11, 2026 at 04:02:41PM +0800, Jianzhou Zhao wrote:
>
>
> Subject: [BUG] fs: KCSAN: data-race in __d_drop / retain_dentry
> Subject: [BUG] fs: KCSAN: data-race in step_into_slowpath / vfs_unlink
> Subject: [BUG] fs/buffer: KCSAN: data-race in __remove_assoc_queue / mark_buffer_dirty_inode
> Subject: [BUG] fs/namei: KCSAN: data-race in path_lookupat / vfs_rename (`d_flags`)
Propose a patch series with fixes and appropriate arguments for adding
these annotations, please. All of the races indicated seem benign.
next prev parent reply other threads:[~2026-03-11 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 8:02 KCSAN: data-race in __d_drop / retain_dentry Jianzhou Zhao
2026-03-11 7:55 ` KCSAN: data-race in step_into_slowpath / vfs_unlink Jianzhou Zhao
2026-03-11 7:49 ` KCSAN: data-race in __remove_assoc_queue / mark_buffer_dirty_inode Jianzhou Zhao
2026-03-11 2:54 ` KCSAN: data-race in path_lookupat / vfs_rename Jianzhou Zhao
2026-03-11 10:38 ` Christian Brauner [this message]
2026-03-17 12:37 ` KCSAN: data-race in __remove_assoc_queue / mark_buffer_dirty_inode Jan Kara
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=20260311-stuben-planbar-ab06185adeaa@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luckd0g@163.com \
--cc=viro@zeniv.linux.org.uk \
/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