summaryrefslogtreecommitdiffstats
path: root/fs/xfs/xfs_log_cil.c
diff options
context:
space:
mode:
authorChandan Babu R <chandanbabu@kernel.org>2024-04-16 09:23:08 +0200
committerChandan Babu R <chandanbabu@kernel.org>2024-04-16 09:23:08 +0200
commit9cb5f15d88d4cbda3bac22769d9e4808bd6cf248 (patch)
tree9b74afbb67bffc160e6522d9f5730befa4a7ef38 /fs/xfs/xfs_log_cil.c
parentMerge tag 'online-fsck-design-6.10_2024-04-15' of https://git.kernel.org/pub/... (diff)
parentxfs: unlock new repair tempfiles after creation (diff)
downloadlinux-9cb5f15d88d4cbda3bac22769d9e4808bd6cf248.tar.xz
linux-9cb5f15d88d4cbda3bac22769d9e4808bd6cf248.zip
Merge tag 'retain-ilock-during-dir-ops-6.10_2024-04-15' of https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux into xfs-6.10-mergeA
xfs: retain ILOCK during directory updates This series changes the directory update code to retain the ILOCK on all files involved in a rename until the end of the operation. The upcoming parent pointers patchset applies parent pointers in a separate chained update from the actual directory update, which is why it is now necessary to keep the ILOCK instead of dropping it after the first transaction in the chain. As a side effect, we no longer need to hold the IOLOCK during an rmapbt scan of inodes to serialize the scan with ongoing directory updates. Signed-off-by: Darrick J. Wong <djwong@kernel.org> Signed-off-by: Chandan Babu R <chandanbabu@kernel.org> * tag 'retain-ilock-during-dir-ops-6.10_2024-04-15' of https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux: xfs: unlock new repair tempfiles after creation xfs: don't pick up IOLOCK during rmapbt repair scan xfs: Hold inode locks in xfs_rename xfs: Hold inode locks in xfs_trans_alloc_dir xfs: Hold inode locks in xfs_ialloc xfs: Increase XFS_QM_TRANS_MAXDQS to 5 xfs: Increase XFS_DEFER_OPS_NR_INODES to 5
Diffstat (limited to 'fs/xfs/xfs_log_cil.c')
0 files changed, 0 insertions, 0 deletions