From: Chandan Babu R Date: Wed, 13 Sep 2023 04:55:00 +0000 (+0530) Subject: Merge tag 'fix-iunlink-6.6_2023-09-12' of https://git.kernel.org/pub/scm/linux/kernel... X-Git-Tag: v6.6.17~3871^2~4 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=fffcdcc31fa1e6374c4d6d2177b7089994fe13b8;p=platform%2Fkernel%2Flinux-rpi.git Merge tag 'fix-iunlink-6.6_2023-09-12' of https://git./linux/kernel/git/djwong/xfs-linux into xfs-6.6-fixesA xfs: reload the last iunlink item It turns out that there are some serious bugs in how xfs handles the unlinked inode lists. Way back before 4.14, there was a bug where a ro mount of a dirty filesystem would recover the log bug neglect to purge the unlinked list. This leads to clean unmounted filesystems with unlinked inodes. Starting around 5.15, we also converted the codebase to maintain a doubly-linked incore unlinked list. However, we never provided the ability to load the incore list from disk. If someone tries to allocate an O_TMPFILE file on a clean fs with a pre-existing unlinked list or even deletes a file, the code will fail and the fs shuts down. This first part of the correction effort adds the ability to load the first inode in the bucket when unlinking a file; and to load the next inode in the list when inactivating (freeing) an inode. Signed-off-by: Darrick J. Wong Signed-off-by: Chandan Babu R * tag 'fix-iunlink-6.6_2023-09-12' of https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux: xfs: load uncached unlinked inodes into memory on demand --- fffcdcc31fa1e6374c4d6d2177b7089994fe13b8