diff options
| author |   Nikolay Borisov <nborisov@suse.com> | 2018-01-08 10:59:43 +0200 |
|---|---|---|
| committer |   David Sterba <dsterba@suse.com> | 2018-03-01 16:16:00 +0100 |
| commit | ac01f26a27f10aace4bb89fd2c2c05a60c251832 (patch) | |
| tree | ec27915237f6e7ad42d31193b175d9bff0d5a036 /fs/btrfs/relocation.c | |
| parent | btrfs: use kvzalloc to allocate btrfs_fs_info (diff) | |
| download | linux-dev-ac01f26a27f10aace4bb89fd2c2c05a60c251832.tar.xz linux-dev-ac01f26a27f10aace4bb89fd2c2c05a60c251832.zip | |
btrfs: handle failure of add_pending_csums
add_pending_csums was added as part of the new data=ordered
implementation in e6dcd2dc9c48 ("Btrfs: New data=ordered
implementation"). Even back then it called the btrfs_csum_file_blocks
which can fail but it never bothered handling the failure. In ENOMEM
situation this could lead to the filesystem failing to write the
checksums for a particular extent and not detect this. On read this
could lead to the filesystem erroring out due to crc mismatch. Fix it by
propagating failure from add_pending_csums and handling them.
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: Josef Bacik <jbacik@fb.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/relocation.c')
0 files changed, 0 insertions, 0 deletions