From: Robbie Ko <robbieko@xxxxxxxxxxxx> This patchset intends to fix btrfs fiemap related bug. The fiemap has the following problems: 1) fiemap: pass correct bytenr when fm_extent_count is zero When user space wants to get the number of file extents, set fm_extent_count to 0 to run fiemap and then read fm_mapped_extents. In the above example, fiemap will return with fm_mapped_extents set to 4, but it should be 1 since there's only one entry in the output. Details can refer to "[PATCH v2 1/2] Btrfs: fiemap: pass correct bytenr when fm_extent_count is zero" 2) fiemap extent SHARED flag error with range clone Currently, only the first extent is checked for shared in extent_map. Here we will check each extent with extent map range, if one of them is shared, extent map is shared. Details can refer to "[PATCH v2 2/2] Btrfs: fix fiemap extent SHARED flag error with range clone." Robbie Ko (2): Btrfs: fiemap: pass correct bytenr when fm_extent_count is zero Btrfs: fix fiemap extent SHARED flag error with range clone. fs/btrfs/extent_io.c | 150 ++++++++++++++++++++++++++++++++++++++++++++------- 1 file changed, 132 insertions(+), 18 deletions(-) -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
