From: Brian Foster <bfoster@redhat.com>
To: fstests@vger.kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH 0/3] xfs: restore and enhance xfs indlen test
Date: Thu, 9 Feb 2017 14:43:41 -0500 [thread overview]
Message-ID: <1486669424-45274-1-git-send-email-bfoster@redhat.com> (raw)
Hi all,
This series is associated with the "buffered write and indlen fixes"
series recently posted to the XFS list. These patches move the original
test to the XFS directory as it now depends on an XFS-specific
mechanism, restore the effectiveness of the original test, and finally
enhance the test to reproduce the newly identified problems fixed by the
kernel patches. Thoughts, reviews, flames appreciated.
Brian
Brian Foster (3):
xfstests: move generic indlen reservation test to xfs dir
tests/xfs: update indlen res. test to use fail writes mechanism
tests/xfs: update indlen res. test to include larger write pattern
tests/generic/033 | 84 --------------------------------------
tests/generic/033.out | 4 --
tests/generic/group | 1 -
tests/xfs/289 | 109 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/289.out | 2 +
tests/xfs/group | 1 +
6 files changed, 112 insertions(+), 89 deletions(-)
delete mode 100755 tests/generic/033
delete mode 100644 tests/generic/033.out
create mode 100755 tests/xfs/289
create mode 100644 tests/xfs/289.out
--
2.7.4
next reply other threads:[~2017-02-09 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 19:43 Brian Foster [this message]
2017-02-09 19:43 ` [PATCH 1/3] xfstests: move generic indlen reservation test to xfs dir Brian Foster
2017-02-09 19:43 ` [PATCH 2/3] tests/xfs: update indlen res. test to use fail writes mechanism Brian Foster
2017-02-09 19:43 ` [PATCH 3/3] tests/xfs: update indlen res. test to include larger write pattern Brian Foster
2017-02-10 7:15 ` [PATCH 0/3] xfs: restore and enhance xfs indlen test Eryu Guan
2017-02-10 13:58 ` Brian Foster
2017-02-10 16:25 ` Darrick J. Wong
2017-02-10 16:32 ` Brian Foster
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=1486669424-45274-1-git-send-email-bfoster@redhat.com \
--to=bfoster@redhat.com \
--cc=fstests@vger.kernel.org \
--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).