]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
ext4: align max orphan file size with e2fsprogs limit
authorBaokun Li <libaokun1@huawei.com>
Thu, 20 Nov 2025 13:42:33 +0000 (21:42 +0800)
committerTheodore Ts'o <tytso@mit.edu>
Wed, 26 Nov 2025 22:13:34 +0000 (17:13 -0500)
commit7c11c56eb32eae96893eebafdbe3decadefe88ad
tree9c0d7fd20d5989c8529c9e808e88e9ffc09627db
parent39fc6d4d3527d790f090dcb10bdb82fd1a1d925a
ext4: align max orphan file size with e2fsprogs limit

Kernel commit 0a6ce20c1564 ("ext4: verify orphan file size is not too big")
limits the maximum supported orphan file size to 8 << 20.

However, in e2fsprogs, the orphan file size is set to 32–512 filesystem
blocks when creating a filesystem.

With 64k block size, formatting an ext4 fs >32G gives an orphan file bigger
than the kernel allows, so mount prints an error and fails:

    EXT4-fs (vdb): orphan file too big: 8650752
    EXT4-fs (vdb): mount failed

To prevent this issue and allow previously created 64KB filesystems to
mount, we updates the maximum allowed orphan file size in the kernel to
512 filesystem blocks.

Fixes: 0a6ce20c1564 ("ext4: verify orphan file size is not too big")
Signed-off-by: Baokun Li <libaokun1@huawei.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Message-ID: <20251120134233.2994147-1-libaokun@huaweicloud.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@kernel.org
fs/ext4/orphan.c