linux-kernel - Re: [PATCH v2 1/2] filelock: use a consume fence in locks_inode

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] [day] [month] [year] [list]

Message-ID: <20251113-dekorativ-wachdienst-5430074100a3@brauner>
Date: Thu, 13 Nov 2025 14:21:48 +0100
From: Christian Brauner <brauner@...nel.org>
To: Mateusz Guzik <mjguzik@...il.com>
Cc: jlayton@...nel.org, viro@...iv.linux.org.uk, jack@...e.cz, 
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] filelock: use a consume fence in
 locks_inode_context()

On Wed, Nov 12, 2025 at 11:44:31AM +0100, Mateusz Guzik wrote:
> Matches the idiom of storing a pointer with a release fence and safely
> getting the content with a consume fence after.
> 
> Eliminates an actual fence on some archs.
> 
> Signed-off-by: Mateusz Guzik <mjguzik@...il.com>
> ---

Can you do me a favor please and redo and resend this on top of:

vfs-6.19.directory.delegations

which has Jeff's changes for this cycle that affect the code you're
changing? Otherwise we get ugly merge conflicts...