btrfs: stop checking for NULL return from btrfs_get_extent_fiemap()
authorJohannes Thumshirn <johannes.thumshirn@wdc.com>
Fri, 4 Feb 2022 12:06:27 +0000 (04:06 -0800)
committerDavid Sterba <dsterba@suse.com>
Mon, 14 Mar 2022 12:13:49 +0000 (13:13 +0100)
commit6b5b7a41d0704f2e3e864b0e4a2539beecefade6
tree0ccb5ea7465f812a52e257e5c2249cbd31d9d5aa
parentf716fa4798df82f858afb9876f6d2e9f37a0d5c7
btrfs: stop checking for NULL return from btrfs_get_extent_fiemap()

In get_extent_skip_holes() we're checking the return of
btrfs_get_extent_fiemap() for an error pointer or NULL, but
btrfs_get_extent_fiemap() will never return NULL, only error pointers or
a valid extent_map.

The other caller of btrfs_get_extent_fiemap(), find_desired_extent(),
correctly only checks for error-pointers.

Reviewed-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/extent_io.c