diff options
| author | Zhang Yi <yi.zhang@huawei.com> | 2025-05-06 09:20:08 +0800 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2025-05-20 10:30:59 -0400 |
| commit | dbe27f06fa38b9bfc598f8864ae1c5d5831d9992 (patch) | |
| tree | 0c90ca78c9f5de5f9d57e17d86f563f6bd4dd8ab /fs/ext4/extents.c | |
| parent | 29ec9bed2395061350249ae356fb300dd82a78e7 (diff) | |
ext4: factor out ext4_get_maxbytes()
There are several locations that get the correct maxbytes value based on
the inode's block type. It would be beneficial to extract a common
helper function to make the code more clear.
Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Reviewed-by: Baokun Li <libaokun1@huawei.com>
Link: https://patch.msgid.link/20250506012009.3896990-3-yi.zhang@huaweicloud.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@kernel.org
Diffstat (limited to 'fs/ext4/extents.c')
| -rw-r--r-- | fs/ext4/extents.c | 7 |
1 files changed, 1 insertions, 6 deletions
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c index 9053fe68ee4c..c42472fd4b63 100644 --- a/fs/ext4/extents.c +++ b/fs/ext4/extents.c @@ -4941,12 +4941,7 @@ static const struct iomap_ops ext4_iomap_xattr_ops = { static int ext4_fiemap_check_ranges(struct inode *inode, u64 start, u64 *len) { - u64 maxbytes; - - if (ext4_test_inode_flag(inode, EXT4_INODE_EXTENTS)) - maxbytes = inode->i_sb->s_maxbytes; - else - maxbytes = EXT4_SB(inode->i_sb)->s_bitmap_maxbytes; + u64 maxbytes = ext4_get_maxbytes(inode); if (*len == 0) return -EINVAL; |