summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@suse.com>2022-09-01 16:18:24 +0300
committerDavid Sterba <dsterba@suse.com>2022-09-26 13:28:00 +0300
commit9a42bbaeff2b101ffdb7fc8c3a326bff08a33917 (patch)
tree6b9e41e5c5acf7cdaee929adda2122e0a08e9d08
parentf12eec9a2665422f4a8e644b4f65475ae2ee5c30 (diff)
downloadlinux-9a42bbaeff2b101ffdb7fc8c3a326bff08a33917.tar.xz
btrfs: remove zero length check when entering fiemap
There's no point to check for a 0 length at extent_fiemap(), as before calling it, we called fiemap_prep() at btrfs_fiemap(), which already checks for a zero length and returns the same -EINVAL error. So remove the pointless check. Reviewed-by: Josef Bacik <josef@toxicpanda.com> Reviewed-by: Qu Wenruo <wqu@suse.com> Signed-off-by: Filipe Manana <fdmanana@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
-rw-r--r--fs/btrfs/extent_io.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
index b5fa92739a5e..8f143c10d81b 100644
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -5455,9 +5455,6 @@ int extent_fiemap(struct btrfs_inode *inode, struct fiemap_extent_info *fieinfo,
u64 em_len = 0;
u64 em_end = 0;
- if (len == 0)
- return -EINVAL;
-
path = btrfs_alloc_path();
if (!path)
return -ENOMEM;