Skip to contentSkip to conversation

ext4: fix check for zero range support in ext4/001

PATCH Superseded Eric Whitney 1 participant 1 message Apr 21, 2014

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 2/3 ext4: fix check for zero range support in ext4/001

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.

---
 tests/ext4/001 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tests/ext4/001 +1 -1
index d575d9a..8239f0e 100755
@@ -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.$$
 
Signature · 6 lines
1.8.3.2

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs