Patch "xfs: report zeroed or not correctly in xfs_zero_range()" has been added to the 4.13-stable tree

This is a note to let you know that I've just added the patch titled

xfs: report zeroed or not correctly in xfs_zero_range()

to the 4.13-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
xfs-report-zeroed-or-not-correctly-in-xfs_zero_range.patch
and it can be found in the queue-4.13 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

From: Eryu Guan <[email protected]>
Date: Mon, 18 Sep 2017 11:39:23 -0700
Subject: xfs: report zeroed or not correctly in xfs_zero_range()

From: Eryu Guan <[email protected]>

commit d20a5e3851969fa685f118a80e4df670255a4e8d upstream.

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.

---
 fs/xfs/xfs_file.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

@@ -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

Patches currently in stable-queue which might be from [email protected] are

queue-4.13/xfs-report-zeroed-or-not-correctly-in-xfs_zero_range.patch queue-4.13/iomap_dio_rw-allocate-aio-completion-queue-before-submitting-dio.patch queue-4.13/xfs-update-i_size-after-unwritten-conversion-in-dio-completion.patch queue-4.13/xfs-trim-writepage-mapping-to-within-eof.patch