commit 441741fc2362b86e1643c3526d8d4c9b8e4b85fb Author: Theodore Ts'o <tytso@mit.edu> Date: Tue Aug 8 16:08:52 2023 -0400 debian: update changelog and debian/patches with additional cherry-picked fixes Signed-off-by: Theodore Ts'o <tytso@mit.edu> commit b9df2bcb4d8a4d2f3985f3d2f9d85292b826cc8b Author: Eric Whitney <enwlinux@gmail.com> Date: Fri Jul 21 14:55:06 2023 -0400 e2fsprogs: modify dumpe2fs to report free block ranges for bigalloc dumpe2fs has never been modified to correctly report block ranges corresponding to free clusters in block allocation bitmaps from bigalloc file systems. Rather than reporting block ranges covering all the blocks in free clusters found in a block bitmap, it either reports just the first block number in a cluster for a single free cluster, or a range beginning with the first block number in the first cluster in a series of free clusters, and ending with the first block number in the last cluster in that series. This behavior causes xfstest shared/298 to fail when run on a bigalloc file system with a 1k block size. The test uses dumpe2fs to collect a list of the blocks freed when files are deleted from a file system. When the test deletes a file containing blocks located after the first block in the last cluster in a series of clusters, dumpe2fs does not report those blocks as free per the test's expectations. Modify dumpe2fs to report full block ranges for free clusters. At the same time, fix a small bug causing unnecessary !in_use() retests while iterating over a block bitmap. Signed-off-by: Eric Whitney <enwlinux@gmail.com> Link: https://lore.kernel.org/r/20230721185506.1020225-1-enwlinux@gmail.com Signed-off-by: Theodore Ts'o <tytso@mit.edu> commit 4565b26ddda4882f7aff032de1d90ce5cd50244f Author: Theodore Ts'o <tytso@mit.edu> Date: Tue Aug 8 15:50:42 2023 -0400 debian: add missing copyright information When the package-specific copyright information was removed, it resulted in some information being lost. It probably makes sence to have all of the licensing information in a single file, so add it back to the debian/copyright file. Fixes: 76f2e8d11582 ("debian: remove package-specific copyright notices") Signed-off-by: Theodore Ts'o <tytso@mit.edu> commit 276bb60252b819db7f297cf429a749e25294dd0f Author: Theodore Ts'o <tytso@mit.edu> Date: Thu Jun 15 00:46:51 2023 -0400 debian: update changelog and debian/patches Update the changelog and debian/patches to reflect the cherry pick of "e2fsck: fix handling of a invalid symlink in an inline_data directory" Signed-off-by: Theodore Ts'o <tytso@mit.edu> commit 4b429d9b4bc76641a46e82f069735a98d0b4774d Author: Theodore Ts'o <tytso@mit.edu> Date: Wed Jun 14 14:44:19 2023 -0400 e2fsck: fix handling of a invalid symlink in an inline_data directory If there is an inline directory that contains a directory entry to an invalid symlink, and that invalid symlink is the portion of the inline directory stored in an xattr portion of the inode, this can result in a buffer overrun. When check_dir_block() is handling the in-xattr portion of the inline directory, it sets the buf pointer to the beginning of that part of the inline directory. This results in the scratch buffer passed to e2fsck_process_bad_inode() to incorrect, resulting in a buffer overrun if e2fsck_pass1_check_symlink() needs to read the symlink target (when the symlink is too long to fit in the i_blocks[] space). This commit fixes this by using the original cd->buf instead of buf, since it can get modified when handling inline directories. Fixes: 0ac4b3973f31 ("e2fsck: inspect inline dir data as two directory blocks") Signed-off-by: Theodore Ts'o <tytso@mit.edu> commit d4745c4ad0044cca269f9bf79b635bb4716c7437 Author: Theodore Ts'o <tytso@mit.edu> Date: Tue May 30 16:20:44 2023 -0400 Update debian/changelog and debian/patches for a tentative 1.47.0-3 release Signed-off-by: Theodore Ts'o <tytso@mit.edu> commit 7c0d0405e6dc8274f163b112a8196a037014b3b9 Author: Theodore Ts'o <tytso@mit.edu> Date: Tue May 30 13:50:52 2023 -0400 e2fsck: Suppress "orphan file is clean" message in preen mode The e2fsck report, "Feature orphan_present is set but orphan file is clean" is intended to request permission before removing the r/o compat feature, orphan_present. However, it is normal if the orphan file is empty, and removing the r/o compat feature is a good thing so that the file system can be mounted on older kernels. When a file system with an orphan_file feature is mounted, the orphan_present feature is set, and it is cleared when the file system is cleanly unmounted. IF the sytstem crashes when there are no inodes in the orphan file, e2fsck should just silently clear the flag in preen mode. Signed-off-by: Theodore Ts'o <tytso@mit.edu> commit bd5f312bc29f4a13d04423fc664794d6bf4f9749 Author: Theodore Ts'o <tytso@mit.edu> Date: Tue May 30 16:03:07 2023 -0400 debian: update debian/patches after reverting the patch for 1.47.0-2 Update the debian/patches directory now that we've reverted the patch disable-metadata_csum_seed-and-orphan_file-by-default. Signed-off-by: Theodore Ts'o <tytso@mit.edu> commit 1fe0370a0671d1bbf568afed5be4dff040792b5e Author: Theodore Ts'o <tytso@mit.edu> Date: Tue May 30 16:01:52 2023 -0400 Revert "Disable metadata_csum_seed and orphan_file by default for Debian" This reverts commit 1181f164c48574a4813bfa203dbd7b4123154021. commit 3fb3d18baba90e5d48d94f4c0b79b2d271b0c913 Author: Theodore Ts'o <tytso@mit.edu> Date: Sat Mar 4 22:16:41 2023 -0500 Update debian/changelog and debian/patches for the 1.47.0-2 release Signed-off-by: Theodore Ts'o <tytso@mit.edu> commit 1181f164c48574a4813bfa203dbd7b4123154021 Author: Theodore Ts'o <tytso@mit.edu> Date: Sat Mar 4 22:04:29 2023 -0500 Disable metadata_csum_seed and orphan_file by default for Debian There are a lot of debian packages that assume that mkfs.ext4 for Debian N will work on Debian N-1 (and sometimes N-2, N-3, etc.). This is a bad assumption, but it's too late to fix this for Debian Bookworm. So revert making these feature a default for now. We will enable it again post Bookworm. Signed-off-by: Theodore Ts'o <tytso@mit.edu>
There is 1 open security issue in bullseye.
You can find information about how to handle this issue in the security team's documentation.