For file extents xfs currently calls xfs_bmapi_read with flag set to 0, meaning extents are going to be truncated to the requested range. Since the same codepath is used for fiemap this means xfs is special in that regard, since other filesystems (ext4/btrfs) do not trim extents for fiemap. Make the behavior consistent by always passing XFS_BMAPI_ENTIRE. A full xfstest run validated that this doesn't regress on ordinary read/write IO. Signed-off-by: Nikolay Borisov <nborisov@xxxxxxxx> --- fs/xfs/xfs_iomap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c index f179bdf1644d..8942324a4d3d 100644 --- a/fs/xfs/xfs_iomap.c +++ b/fs/xfs/xfs_iomap.c @@ -1008,7 +1008,7 @@ xfs_file_iomap_begin( end_fsb = XFS_B_TO_FSB(mp, offset + length); error = xfs_bmapi_read(ip, offset_fsb, end_fsb - offset_fsb, &imap, - &nimaps, 0); + &nimaps, XFS_BMAPI_ENTIRE); if (error) goto out_unlock; -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
