From: Christian Brauner <brauner@kernel.org>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
viro@zeniv.linux.org.uk, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: retire stale lock ordering annotations from inode hash
Date: Mon, 27 Apr 2026 16:44:05 +0200 [thread overview]
Message-ID: <20260427-bauzeit-beipflichten-35fc65e409f9@brauner> (raw)
In-Reply-To: <20260423170431.1483370-1-mjguzik@gmail.com>
On Thu, 23 Apr 2026 19:04:31 +0200, Mateusz Guzik wrote:
> 1. iunique does not take the hash lock as of:
> 3f19b2ab97a97b41 ("vfs, afs, ext4: Make the inode hash table RCU searchable")
> 2. s_inode_list_lock is no longer taken under the hash lock as of:
> c918f15420e336a9 ("fs: call inode_sb_list_add() outside of inode hash lock")
Applied to the vfs-7.2.inode branch of the vfs/vfs.git tree.
Patches in the vfs-7.2.inode 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-7.2.inode
[1/1] fs: retire stale lock ordering annotations from inode hash
https://git.kernel.org/vfs/vfs/c/8edf31f99a20
prev parent reply other threads:[~2026-04-27 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 17:04 [PATCH] fs: retire stale lock ordering annotations from inode hash Mateusz Guzik
2026-04-27 9:25 ` Jan Kara
2026-04-27 14:44 ` Christian Brauner [this message]
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=20260427-bauzeit-beipflichten-35fc65e409f9@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.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