From: Chandan Babu R Date: Tue, 16 Apr 2024 07:12:17 +0000 (+0530) Subject: Merge tag 'inode-repair-improvements-6.10_2024-04-15' of https://git.kernel.org/pub... X-Git-Tag: v6.10-rc1~87^2~61 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9ba8e658d867be96f9da58f060deff1e9cbca1a9;p=thirdparty%2Fkernel%2Flinux.git Merge tag 'inode-repair-improvements-6.10_2024-04-15' of https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux into xfs-6.10-mergeA xfs: inode-related repair fixes While doing QA of the online fsck code, I made a few observations: First, nobody was checking that the di_onlink field is actually zero; Second, that allocating a temporary file for repairs can fail (and thus bring down the entire fs) if the inode cluster is corrupt; and Third, that file link counts do not pin at ~0U to prevent integer overflows. Fourth, the x{chk,rep}_metadata_inode_fork functions should be subclassing the main scrub context, not modifying the parent's setup willy-nilly. This scattered patchset fixes those three problems. Signed-off-by: Darrick J. Wong Signed-off-by: Chandan Babu R * tag 'inode-repair-improvements-6.10_2024-04-15' of https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux: xfs: create subordinate scrub contexts for xchk_metadata_inode_subtype xfs: pin inodes that would otherwise overflow link count xfs: try to avoid allocating from sick inode clusters xfs: check unused nlink fields in the ondisk inode --- 9ba8e658d867be96f9da58f060deff1e9cbca1a9