Re: [PATCH 1/2] xfs: report zeroed or not correctly in xfs_zero_range()
From: Carlos Maiolino <hidden>
Date: 2017-09-07 08:49:35
On Thu, Sep 07, 2017 at 11:42:53AM +0800, Eryu Guan wrote:
The 'did_zero' param of xfs_zero_range() was not passed to
iomap_zero_range() correctly. This was introduced by commit
7bb41db3ea16 ("xfs: handle 64-bit length in xfs_iozero"), and found
by code inspection.Looks good, Reviewed-by: Carlos Maiolino <redacted>
quoted hunk ↗ jump to hunk
Signed-off-by: Eryu Guan <redacted> --- fs/xfs/xfs_file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c index c4893e226fd8..812cd17b331f 100644 --- a/fs/xfs/xfs_file.c +++ b/fs/xfs/xfs_file.c@@ -58,7 +58,7 @@ xfs_zero_range( xfs_off_t count, bool *did_zero) { - return iomap_zero_range(VFS_I(ip), pos, count, NULL, &xfs_iomap_ops); + return iomap_zero_range(VFS_I(ip), pos, count, did_zero, &xfs_iomap_ops); } int-- 2.13.5 -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
-- Carlos