xfs
[Top] [All Lists]

[PATCH] ext4: fix check for zero range support in ext4/001

To: xfs@xxxxxxxxxxx
Subject: [PATCH] ext4: fix check for zero range support in ext4/001
From: Eric Whitney <enwlinux@xxxxxxxxx>
Date: Sat, 19 Apr 2014 15:08:15 -0400
Cc: linux-ext4@xxxxxxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=PicNx70b+YaGn41Kv03fMGiuOb4RFUcLLJpRR4WoACM=; b=sEM0Ymu9mVvdCMptVmTtKr0TUZ8D/9/aznEDsEcNSWcKw2a/rL/OSIJwP/EFEQQ25t t88f2iOn3CmIb6FNSzY+jVjfo8kIqKVLovYax/spA5cDnCrndyODQwRO3oKb+hHmWf+o 3JVzEx0ZatGdBzztnzVp9R7AJ9ON6ZNgW5lfS9KnUEOcfQb14X2lhHbAW81j4ynfeWs8 XebX3fNP1Vi4P/zIJvqtktD8BQtW9QFOZHH4ND4XkO2O0Sk3idNWMA2PbOnsyGRHQ2Lp uCA6vxrrMWeZY+3eK0WGaZE1KHC7rcKiJXgz622BuJje3fFDfLdawIRt2PTnpdiSv0WO GHCg==
User-agent: Mutt/1.5.21 (2010-09-15)
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 <enwlinux@xxxxxxxxx>
---
 tests/ext4/001 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/ext4/001 b/tests/ext4/001
index d575d9a..827d806 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_command "fzero"
 
 testfile=$TEST_DIR/001.$$
 
-- 
1.8.3.2

<Prev in Thread] Current Thread [Next in Thread>