diff options
author | Johannes Thumshirn <jthumshirn@suse.de> | 2019-05-22 10:19:01 +0200 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2019-07-01 13:35:00 +0200 |
commit | 1e25a2e3ca0dab0ed1030570e95d98af47113eae (patch) | |
tree | ff9d51c831b177b75d4abd939159a8341883edcb /fs/btrfs/disk-io.c | |
parent | 4bb3c2e2b5bb0d57f7d11f2da829357c5ca628a4 (diff) | |
download | linux-1e25a2e3ca0dab0ed1030570e95d98af47113eae.tar.gz linux-1e25a2e3ca0dab0ed1030570e95d98af47113eae.tar.bz2 linux-1e25a2e3ca0dab0ed1030570e95d98af47113eae.zip |
btrfs: don't assume ordered sums to be 4 bytes
BTRFS has the implicit assumption that a checksum in btrfs_orderd_sums
is 4 bytes. While this is true for CRC32C, it is not for any other
checksum.
Change the data type to be a byte array and adjust loop index
calculation accordingly.
This includes moving the adjustment of 'index' by 'ins_size' in
btrfs_csum_file_blocks() before dividing 'ins_size' by the checksum
size, because before this patch the 'sums' member of 'struct
btrfs_ordered_sum' was 4 Bytes in size and afterwards it is only one
byte.
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/disk-io.c')
0 files changed, 0 insertions, 0 deletions