All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: fstests@vger.kernel.org
Cc: Xiao Yang <yangx.jy@cn.fujitsu.com>
Subject: [PATCH] ext4/306: require 64bit feature to run ext4/306
Date: Wed, 1 Mar 2017 15:57:02 +0800	[thread overview]
Message-ID: <1488355022-22218-1-git-send-email-yangx.jy@cn.fujitsu.com> (raw)

The 64bit feature isn't supported by mkfs.ext4 on RHEL6, so
we add _require_ext4_mkfs_64bit to check it.  If 64bit feature
isn't supported, we could skip this case.  This feature has
been produced by 'commit 02d6f47e9647d ("mke2fs: Fix up mke2fs
to be able to make 64-bit file systems")'.

Signed-off-by: Xiao Yang <yangx.jy@cn.fujitsu.com>
---
 common/rc      | 7 +++++++
 tests/ext4/306 | 1 +
 2 files changed, 8 insertions(+)

diff --git a/common/rc b/common/rc
index 8f23334..0c3c154 100644
--- a/common/rc
+++ b/common/rc
@@ -1669,6 +1669,13 @@ _require_scratch_ext4_crc()
 	_scratch_unmount
 }
 
+# this test requires the 64bit feature to be available in mkfs.ext4
+_require_ext4_mkfs_64bit()
+{
+	$MKFS_EXT4_PROG -F -O 64bit -n $SCRATCH_DEV 512m >/dev/null 2>&1 \
+	   || _notrun "mkfs.ext4 doesn't have 64bit feature"
+}
+
 # this test requires the bigalloc feature to be available in mkfs.ext4
 #
 _require_ext4_mkfs_bigalloc()
diff --git a/tests/ext4/306 b/tests/ext4/306
index fa3b782..4a92dd2 100755
--- a/tests/ext4/306
+++ b/tests/ext4/306
@@ -44,6 +44,7 @@ _supported_fs ext4
 _supported_os Linux
 
 _require_scratch
+_require_ext4_mkfs_64bit
 
 rm -f $seqres.full
 
-- 
1.8.3.1




             reply	other threads:[~2017-03-01  8:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01  7:57 Xiao Yang [this message]
2017-03-01  8:59 ` [PATCH] ext4/306: require 64bit feature to run ext4/306 Eryu Guan
2017-03-02  2:24   ` [PATCH v2] " Xiao Yang
2017-03-02  4:22     ` Eryu Guan
2017-03-02  4:37       ` Xiao Yang
2017-03-02  6:03       ` [PATCH v3] ext4: add _require_ext4_mkfs_feature to check different features Xiao Yang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1488355022-22218-1-git-send-email-yangx.jy@cn.fujitsu.com \
    --to=yangx.jy@cn.fujitsu.com \
    --cc=fstests@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.