On Thu, 20 Mar 2025 01:46:43 +0100, Mateusz Guzik wrote: > As both locks are highly contended during significant inode churn, > holding the inode hash lock while waiting for the sb list lock > exacerbates the problem. > > Why moving it out is safe: the inode at hand still has I_NEW set and > anyone who finds it through legitimate means waits for the bit to clear, > by which time inode_sb_list_add() is guaranteed to have finished. > > [...] Applied to the vfs-6.15.misc branch of the vfs/vfs.git tree. Patches in the vfs-6.15.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.15.misc [1/1] fs: call inode_sb_list_add() outside of inode hash lock https://git.kernel.org/vfs/vfs/c/c918f15420e3
