| commit | ad60ed92d1e0edca2769754c3a50129571a0e49d | |
| author | Qu Wenruo <quwenruo@cn.fujitsu.com> | |
| Fri, 17 Mar 2017 02:06:33 +0000 (17 10:06 +0800) | ||
| committer | David Sterba <dsterba@suse.com> | |
| Fri, 31 Mar 2017 12:17:48 +0000 (31 14:17 +0200) | ||
| tree | 057ad9fa95a40a4c781761371f14edf08278e251 | treesnapshot (tar.gz zip) |
| parent | 52bbb015e5a21743478024becb1c3dacea822adb | commitdiff |
btrfs-progs: check: lowmem, fix false alert about backref lost for SHARED_DATA_REF
In check_extent_data_item(), after checking extent item of one data
extent, we search inlined data backref, then EXTENT_DATA_REF_KEY.
But we didn't search SHARED_DATA_REF, so if the backref is
SHARED_DATA_REF, then we will raise a false alert about backref lost.
Fix by also checking SHARED_DATA_REF_KEY in check_extent_data_item().
Reported-by: Chris Murphy <chris@colorremedies.com>
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
Signed-off-by: David Sterba <dsterba@suse.com>
In check_extent_data_item(), after checking extent item of one data
extent, we search inlined data backref, then EXTENT_DATA_REF_KEY.
But we didn't search SHARED_DATA_REF, so if the backref is
SHARED_DATA_REF, then we will raise a false alert about backref lost.
Fix by also checking SHARED_DATA_REF_KEY in check_extent_data_item().
Reported-by: Chris Murphy <chris@colorremedies.com>
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
Signed-off-by: David Sterba <dsterba@suse.com>
| cmds-check.c | diffblobblamehistory |