ext4: fast commit may miss tracking unwritten range during ftruncate
authorXin Yin <yinxin.x@bytedance.com>
Thu, 23 Dec 2021 03:23:37 +0000 (11:23 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 27 Jan 2022 11:02:49 +0000 (12:02 +0100)
commit 9725958bb75cdfa10f2ec11526fdb23e7485e8e4 upstream.

If use FALLOC_FL_KEEP_SIZE to alloc unwritten range at bottom, the
inode->i_size will not include the unwritten range. When call
ftruncate with fast commit enabled, it will miss to track the
unwritten range.

Change to trace the full range during ftruncate.

Signed-off-by: Xin Yin <yinxin.x@bytedance.com>
Reviewed-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Link: https://lore.kernel.org/r/20211223032337.5198-3-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/inode.c

index 0e72ceec0fc6a7f30b81817c2e1a8f2a5f763090..755ee6c54ff7cf7890655876f8466d345a886126 100644 (file)
@@ -5428,8 +5428,7 @@ int ext4_setattr(struct user_namespace *mnt_userns, struct dentry *dentry,
                                ext4_fc_track_range(handle, inode,
                                        (attr->ia_size > 0 ? attr->ia_size - 1 : 0) >>
                                        inode->i_sb->s_blocksize_bits,
-                                       (oldsize > 0 ? oldsize - 1 : 0) >>
-                                       inode->i_sb->s_blocksize_bits);
+                                       EXT_MAX_BLOCKS - 1);
                        else
                                ext4_fc_track_range(
                                        handle, inode,