From: Allison Henderson <allison.henderson@oracle.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH v2 0/1] Parent pointers test v2
Date: Wed, 26 Sep 2018 03:28:04 -0700 [thread overview]
Message-ID: <1537957685-10753-1-git-send-email-allison.henderson@oracle.com> (raw)
Hi all,
This is the 2nd revision of a new xfstest group to exercise the parent
pointer code. These tests cover basic parent pointer operations,
including link, unlink, rename, overwrite, hardlinks and error inject.
Points of intrest since v1:
I've split the test into 3 different tests. The first runs through
simple link, unlink, rename, and overwrite operations. The next
test exercises handling multiple parent points with hardlinks, and
the last test exercises the error inject and recovery. These
tests use the new flags in the xfsprogs set which helped to drop
the run time from a minute down to a few seconds. I've also
factored out some of the common code into a new common/parent
file.
As always, comments and feedback are appreciated. Thank you!
Allison
Allison Henderson (1):
xfstests: Add parent pointer test
common/parent | 196 +++++++++++
common/rc | 3 +
tests/xfs/491 | 156 +++++++++
tests/xfs/491.out | 70 ++++
tests/xfs/492 | 134 +++++++
tests/xfs/492.out | 1009 +++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/493 | 143 ++++++++
tests/xfs/493.out | 27 ++
tests/xfs/group | 4 +
9 files changed, 1742 insertions(+)
create mode 100644 common/parent
create mode 100755 tests/xfs/491
create mode 100644 tests/xfs/491.out
create mode 100755 tests/xfs/492
create mode 100644 tests/xfs/492.out
create mode 100755 tests/xfs/493
create mode 100644 tests/xfs/493.out
--
2.7.4
next reply other threads:[~2018-09-26 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 10:28 Allison Henderson [this message]
2018-09-26 10:28 ` [PATCH v2 1/1] xfstests: Add parent pointer test Allison Henderson
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=1537957685-10753-1-git-send-email-allison.henderson@oracle.com \
--to=allison.henderson@oracle.com \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).