From: "Theodore Ts'o" <tytso@mit.edu>
To: fstests@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>
Subject: [PATCH] common: introduce XFS_IO_AVOID env var
Date: Sat, 17 Oct 2015 14:45:18 -0400 [thread overview]
Message-ID: <1445107518-32022-1-git-send-email-tytso@mit.edu> (raw)
Like FSSTRESS_AVOID and FSX_AVOID, XFS_IO_AVOID can be used to avoid
using various advanced file system features such as "fpunch"
"fcollapse", "finsert", or "zero". Tests that require an xfs_io
command which is included in the space-separated list found in the
XFS_IO_AVOID environment variable will be skipped using _notrun.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
---
README | 4 ++++
common/rc | 5 +++++
2 files changed, 9 insertions(+)
diff --git a/README b/README
index f8a878c..bb0075b 100644
--- a/README
+++ b/README
@@ -78,6 +78,10 @@ Preparing system for tests (IRIX and Linux):
added to the end of fsstresss and fsx invocations, respectively,
in case you wish to exclude certain operational modes from these
tests.
+ - setenv XFS_IO_AVOID which may contain a list of space separated
+ xfs_io commands which will be avoided in case you want to
+ exclude tests that require the use of certain file system
+ operations such as "fpunch", "fcollapse", "finsert", or "zero".
- or add a case to the switch in common/config assigning
these variables based on the hostname of your test
diff --git a/common/rc b/common/rc
index adf1edf..61de97e 100644
--- a/common/rc
+++ b/common/rc
@@ -1603,6 +1603,11 @@ _require_xfs_io_command()
fi
command=$1
+ if echo "$XFS_IO_AVOID" | grep -wq "$command"
+ then
+ _notrun "Avoiding xfs_io $command"
+ fi
+
testfile=$TEST_DIR/$$.xfs_io
case $command in
"falloc" )
--
2.5.0
next reply other threads:[~2015-10-17 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 18:45 Theodore Ts'o [this message]
2015-10-18 21:37 ` [PATCH] common: introduce XFS_IO_AVOID env var Dave Chinner
2015-10-18 22:08 ` Theodore Ts'o
2015-10-18 23:14 ` Dave Chinner
2015-10-19 0:10 ` Theodore Ts'o
2015-10-19 2:29 ` Dave Chinner
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=1445107518-32022-1-git-send-email-tytso@mit.edu \
--to=tytso@mit.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox