btrfs: Don't hardcode the csum size in btrfs_ordered_sum_size
authorNikolay Borisov <nborisov@suse.com>
Wed, 7 Feb 2018 09:19:10 +0000 (11:19 +0200)
committerDavid Sterba <dsterba@suse.com>
Mon, 26 Mar 2018 13:09:29 +0000 (15:09 +0200)
commitaf89e0dc2ce3177d07c4af4028b8a7b88733d07e
tree68ff5d58bf2799696d63122bcb6b24b3ef256f88
parent97dc231e8990d484874e75e9f30a2f11fcf035c2
btrfs: Don't hardcode the csum size in btrfs_ordered_sum_size

Currently the function uses a hardcoded value for the checksum size of
a sector. This is fine, given that we currently support only a single
algorithm, whose checksum is 4 bytes == sizeof(u32). Despite not
having other algorithms, btrfs' design supports using a different
algorithm whith different space requirements. To future-proof the code
query the size of the currently used algorithm from the in-memory copy
of the super block. No functional changes.

Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: Su Yue <suy.fnst@cn.fujitsu.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/ordered-data.h