From: Jeff Layton <jlayton@kernel.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [xfstests PATCH] gfs2: allow testing with gfs2
Date: Wed, 26 Jul 2017 14:43:31 -0400 [thread overview]
Message-ID: <20170726184331.27953-1-jlayton@kernel.org> (raw)
From: Jeff Layton <jlayton@redhat.com>
For now, just have it avoid locking. With a fixed kernel,
generic/441 now passes.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
---
common/config | 1 +
common/rc | 7 +++++++
tests/generic/441 | 2 +-
3 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/common/config b/common/config
index 5091db9d5099..eb32efc105db 100644
--- a/common/config
+++ b/common/config
@@ -244,6 +244,7 @@ case "$HOSTOS" in
export MKFS_REISER4_PROG="`set_prog_path mkfs.reiser4`"
export E2FSCK_PROG="`set_prog_path e2fsck`"
export TUNE2FS_PROG="`set_prog_path tune2fs`"
+ export MKFS_GFS2_PROG="`set_prog_path mkfs.gfs2`"
;;
esac
diff --git a/common/rc b/common/rc
index bd989bb5f4dd..70bb39225368 100644
--- a/common/rc
+++ b/common/rc
@@ -158,6 +158,9 @@ case "$FSTYP" in
ext4)
[ "$MKFS_EXT4_PROG" = "" ] && _fatal "mkfs.ext4 not found"
;;
+ gfs2)
+ [ "$MKFS_GFS2_PROG" = "" ] && _fatal "mkfs.gfs2 not found"
+ ;;
f2fs)
[ "$MKFS_F2FS_PROG" = "" ] && _fatal "mkfs.f2fs not found"
;;
@@ -861,6 +864,10 @@ _scratch_mkfs()
mkfs_cmd="yes | $MKFS_PROG -t $FSTYP --"
mkfs_filter="grep -v -e ^mkfs\.ocfs2"
;;
+ gfs2)
+ mkfs_cmd="$MKFS_GFS2_PROG -p lock_nolock -O"
+ mkfs_filter="cat"
+ ;;
*)
mkfs_cmd="yes | $MKFS_PROG -t $FSTYP --"
mkfs_filter="cat"
diff --git a/tests/generic/441 b/tests/generic/441
index 075d87723ca1..b98f709cb6eb 100755
--- a/tests/generic/441
+++ b/tests/generic/441
@@ -55,7 +55,7 @@ case $FSTYP in
btrfs)
_notrun "btrfs has a specialized test for this"
;;
- ext3|ext4|xfs)
+ ext3|ext4|gfs2|xfs)
# Do the more thorough test if we have a logdev
_has_logdev && sflag=''
;;
--
2.13.3
next reply other threads:[~2017-07-26 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 18:43 Jeff Layton [this message]
2017-07-27 5:18 ` [Cluster-devel] [xfstests PATCH] gfs2: allow testing with gfs2 Eryu Guan
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=20170726184331.27953-1-jlayton@kernel.org \
--to=jlayton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).