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 Feb 2022 15:36:02 +0000 (16:36 +0100)
commite5b101a36780a889b2d04ce619cdb110f771d84d
treeb20f4feeaac17ccd0698c608565561744df967a9
parente4e5efc9af5799af213d117297b92f86b3761fde
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