[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251204-flurbeleuchtung-lager-7960aaee15c1@brauner>
Date: Thu, 4 Dec 2025 10:14:09 +0100
From: Christian Brauner <brauner@...nel.org>
To: Mateusz Guzik <mjguzik@...il.com>
Cc: Christian Brauner <brauner@...nel.org>,
viro@...iv.linux.org.uk,
jack@...e.cz,
linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org,
Jeff Layton <jlayton@...nel.org>
Subject: Re: [PATCH v4 1/2] filelock: use a consume fence in locks_inode_context()
On Wed, 03 Dec 2025 10:48:36 +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.
>
>
Applied to the vfs-6.20.misc branch of the vfs/vfs.git tree.
Patches in the vfs-6.20.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.20.misc
[1/2] filelock: use a consume fence in locks_inode_context()
https://git.kernel.org/vfs/vfs/c/dc6f30a29da7
[2/2] fs: track the inode having file locks with a flag in ->i_opflags
https://git.kernel.org/vfs/vfs/c/26193099d06f
Powered by blists - more mailing lists