| commit | 0d1e0bead62a1778c45f22439cf067e63068faea | |
| author | Liu Bo <bo.li.liu@oracle.com> | |
| Tue, 11 Jul 2017 20:43:16 +0000 (11 14:43 -0600) | ||
| committer | David Sterba <dsterba@suse.com> | |
| Wed, 16 Aug 2017 14:12:02 +0000 (16 16:12 +0200) | ||
| tree | e2340e7e969bfb8a506ef193adaae243d9d65a08 | treesnapshot (tar.gz zip) |
| parent | 69f03f137a1cb1a5215bc9e64597bfdfcdf22fde | commitdiff |
Btrfs: report errors when checksum is not found
When btrfs fails the checksum check, it'll fill the whole page with
"1".
However, if %csum_expected is 0 (which means there is no checksum), then
for some unknown reason, we just pretend that the read is correct, so
userspace would be confused about the dilemma that read is successful but
getting a page with all content being "1".
This can happen due to a bug in btrfs-convert.
This fixes it by always returning errors if checksum doesn't match.
Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
When btrfs fails the checksum check, it'll fill the whole page with
"1".
However, if %csum_expected is 0 (which means there is no checksum), then
for some unknown reason, we just pretend that the read is correct, so
userspace would be confused about the dilemma that read is successful but
getting a page with all content being "1".
This can happen due to a bug in btrfs-convert.
This fixes it by always returning errors if checksum doesn't match.
Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
| fs/btrfs/inode.c | diffblobblamehistory |