ext4: fix fast commit may miss tracking range for FALLOC_FL_ZERO_RANGE
authorXin Yin <yinxin.x@bytedance.com>
Tue, 21 Dec 2021 02:28:39 +0000 (10:28 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 27 Jan 2022 10:05:16 +0000 (11:05 +0100)
commit50bc43bc1ce0821e7042ab5ffb7a943e0ef854ba
treef0f8f057fc0f2a73e2a87b866a729dfe53c0ade4
parent85cc4554eea845ae0a1b06f43df6b566ff6776d2
ext4: fix fast commit may miss tracking range for FALLOC_FL_ZERO_RANGE

commit 5e4d0eba1ccaf19f93222abdeda5a368be141785 upstream.

when call falloc with FALLOC_FL_ZERO_RANGE, to set an range to unwritten,
which has been already initialized. If the range is align to blocksize,
fast commit will not track range for this change.

Also track range for unwritten range in ext4_map_blocks().

Signed-off-by: Xin Yin <yinxin.x@bytedance.com>
Reviewed-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Link: https://lore.kernel.org/r/20211221022839.374606-1-yinxin.x@bytedance.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/ext4/extents.c
fs/ext4/inode.c