summaryrefslogtreecommitdiffstats
path: root/fs/netfs
diff options
context:
space:
mode:
authorQu Wenruo <wqu@suse.com>2022-09-16 15:28:37 +0800
committerDavid Sterba <dsterba@suse.com>2022-12-05 18:00:47 +0100
commita196a8944f77b7b762795a0862d8aa4a005625a4 (patch)
tree0393b6d1782724684dc0b121ea02614307b555ea /fs/netfs
parentaffc5424338682641829cc84293ec90f36425034 (diff)
downloadlinux-a196a8944f77b7b762795a0862d8aa4a005625a4.tar.gz
linux-a196a8944f77b7b762795a0862d8aa4a005625a4.tar.bz2
linux-a196a8944f77b7b762795a0862d8aa4a005625a4.zip
btrfs: do not reset extent map members for inline extents read
Currently for inline extents read inside btrfs_get_extent(), we will reset several extent map members: - em->start Reset to extent_start, which is completely unnecessary. The extent_start and em->start should have already be zero, ensured by tree-checker already. - em->len Reset the round_up(copy_size, fs_info->sectorsize), which is again unnecessary. - em->orig_block_len Reset to em->len (sectorsize), while it is originally unset from btrfs_extent_item_to_extent_map(). This makes no difference, as all extent map handling paths will ignore the orig_block_len if they found it's an inlined extent. Such inline extent orig_block_len ignoring examples can be found in btrfs_drop_extent_cache(). - em->orig_start Reset to em->start (0), while it is originally set to EXTENT_MAP_HOLE. This makes no difference either, as all extent map handling paths will ignore the em->orig_start if they found it's an inline extent. Thus all these em members resetting are unnecessary. Replace them with ASSERT()s checking the only two members (block_start and length) that make sense. Signed-off-by: Qu Wenruo <wqu@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/netfs')
0 files changed, 0 insertions, 0 deletions