]> git.ipfire.org Git - thirdparty/linux.git/commit
ext4: correct the mapping status if the extent has been zeroed
authorZhang Yi <yi.zhang@huawei.com>
Sat, 29 Nov 2025 10:32:36 +0000 (18:32 +0800)
committerTheodore Ts'o <tytso@mit.edu>
Sun, 18 Jan 2026 16:23:33 +0000 (11:23 -0500)
commit5f1a1cccebf87e6c51f981908cc3cc10c3bc936b
treef26da7bc93993083d82847b4eea98f3101e79d17
parentfeaf2a80e78f89ee8a3464126077ba8683b62791
ext4: correct the mapping status if the extent has been zeroed

Before submitting I/O and allocating blocks with the
EXT4_GET_BLOCKS_PRE_IO flag set, ext4_split_convert_extents() may
convert the target extent range to initialized due to ENOSPC, ENOMEM, or
EQUOTA errors. However, it still marks the mapping as incorrectly
unwritten. Although this may not seem to cause any practical problems,
it will result in an unnecessary extent conversion operation after I/O
completion. Therefore, it's better to correct the returned mapping
status.

Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
Reviewed-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Reviewed-by: Baokun Li <libaokun1@huawei.com>
Message-ID: <20251129103247.686136-5-yi.zhang@huaweicloud.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
fs/ext4/extents.c