ext4: fix check for zero range support in ext4/001
PATCH 1/1 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.
--- tests/ext4/001 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tests/ext4/001 +1 -1
@@ -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_command "fzero" testfile=$TEST_DIR/001.$$
Signature · 1 line
1.8.3.2
Quoted 7 lines · Eric Whitney
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.Signed-off-by Eric Whitney <[email protected]>
LGTM
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs