linux-kernel - Re: [PATCH 5.10 0/5] kernfs: backport locking and concurrency improvement

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2025052103-headband-friend-90f6@gregkh>
Date: Wed, 21 May 2025 06:15:41 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Qingfang Deng <dqfext@...il.com>
Cc: stable@...r.kernel.org, Tejun Heo <tj@...nel.org>,
	linux-kernel@...r.kernel.org, Ian Kent <raven@...maw.net>
Subject: Re: [PATCH 5.10 0/5] kernfs: backport locking and concurrency
 improvement

On Wed, May 21, 2025 at 09:53:30AM +0800, Qingfang Deng wrote:
> KCSAN reports concurrent accesses to inode->i_mode:

<snip>

Yes, but can you actually trigger this issue with a real workload?  How
were these tested in the 5.10 tree, and if this is a problem, can you
just move to a newer release instead?

thanks,

greg k-h