* [PATCH v2 2/3] ext4: fix check for zero range support in ext4/001
@ 2014-04-21 20:43 Eric Whitney
0 siblings, 0 replies; only message in thread
From: Eric Whitney @ 2014-04-21 20:43 UTC (permalink / raw)
To: xfs; +Cc: linux-ext4
Ext4/001 fails when run on a file system that does not support byte range
zeroing. For example, an EOPNOTSUPP failure occurs when the test is run
on a pre-3.15 extent-mapped file system. The code in the test intended
to prevent this contains an apparent typo that results in a check for
fallocate() rather than zero range support.
v2: Use new wrapper function for the check.
Signed-off-by: Eric Whitney <enwlinux@gmail.com>
---
tests/ext4/001 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/ext4/001 b/tests/ext4/001
index d575d9a..8239f0e 100755
--- a/tests/ext4/001
+++ b/tests/ext4/001
@@ -45,7 +45,7 @@ trap "_cleanup ; exit \$status" 0 1 2 3 15
# real QA test starts here
_supported_fs ext4
_supported_os Linux
-_require_xfs_io_falloc "fzero"
+_require_xfs_io_falloc_zero
testfile=$TEST_DIR/001.$$
--
1.8.3.2
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2014-04-21 20:43 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-04-21 20:43 [PATCH v2 2/3] ext4: fix check for zero range support in ext4/001 Eric Whitney
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.