From: Jeff Layton <jlayton@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@ZenIV.linux.org.uk>, Jan Kara <jack@suse.cz>,
tytso@mit.edu, axboe@kernel.dk, mawilcox@microsoft.com,
ross.zwisler@linux.intel.com, corbet@lwn.net,
Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
David Sterba <dsterba@suse.com>,
"Darrick J . Wong" <darrick.wong@oracle.com>
Cc: Carlos Maiolino <cmaiolino@redhat.com>,
Eryu Guan <eguan@redhat.com>, David Howells <dhowells@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-block@vger.kernel.org
Subject: [xfstests PATCH v5 0/5] new tests for writeback error reporting behavior
Date: Fri, 16 Jun 2017 15:36:14 -0400 [thread overview]
Message-ID: <20170616193619.14576-1-jlayton@redhat.com> (raw)
The main changes in this set from the last are:
- add a btrfs/999.out file
- use _supported_fs to whitelist fs' on which the tests should run
- fix the ext3/4 mount option handling when creating journal device
- ensure that dmerror is installed on make install
These tests are intended to test the new writeback error reporting
introduced by this kernel patchset:
[PATCH v7 00/22] fs: enhanced writeback error reporting with errseq_t (pile #1)
It adds 3 new xfstests for testing kernel behavior when writeback from
the pagecache fails: one generic filesystem test, one test for raw block
devices and one test for btrfs.
The tests work with dmerror to make data writeback from the pagecache
fail, and then tests how the kernel reports errors afterward.
xfs, ext2/3/4 and btrfs all pass on a kernel with the patchset above. "Bare"
block devices also work correctly.
Jeff Layton (5):
ext4: allow ext4 to use $SCRATCH_LOGDEV
ext3: allow it to put journal on a separate device when doing
scratch_mkfs
generic: add a writeback error handling test
generic: test writeback error handling on dmerror devices
btrfs: make a btrfs version of writeback error reporting test
.gitignore | 1 +
common/dmerror | 13 ++-
common/rc | 14 ++-
doc/auxiliary-programs.txt | 16 ++++
src/Makefile | 4 +-
src/dmerror | 44 +++++++++
src/fsync-err.c | 223 +++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/999 | 94 +++++++++++++++++++
tests/btrfs/999.out | 3 +
tests/btrfs/group | 1 +
tests/generic/998 | 63 +++++++++++++
tests/generic/998.out | 2 +
tests/generic/999 | 84 +++++++++++++++++
tests/generic/999.out | 3 +
tests/generic/group | 2 +
15 files changed, 559 insertions(+), 8 deletions(-)
create mode 100755 src/dmerror
create mode 100644 src/fsync-err.c
create mode 100755 tests/btrfs/999
create mode 100644 tests/btrfs/999.out
create mode 100755 tests/generic/998
create mode 100644 tests/generic/998.out
create mode 100755 tests/generic/999
create mode 100644 tests/generic/999.out
--
2.13.0
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-06-16 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 19:36 Jeff Layton [this message]
2017-06-16 19:36 ` [xfstests PATCH v5 1/5] ext4: allow ext4 to use $SCRATCH_LOGDEV Jeff Layton
2017-06-16 19:36 ` [xfstests PATCH v5 2/5] ext3: allow it to put journal on a separate device when doing scratch_mkfs Jeff Layton
2017-06-16 19:36 ` [xfstests PATCH v5 3/5] generic: add a writeback error handling test Jeff Layton
2017-06-16 19:36 ` [xfstests PATCH v5 4/5] generic: test writeback error handling on dmerror devices Jeff Layton
2017-06-16 19:36 ` [xfstests PATCH v5 5/5] btrfs: make a btrfs version of writeback error reporting test Jeff Layton
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=20170616193619.14576-1-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=clm@fb.com \
--cc=cmaiolino@redhat.com \
--cc=corbet@lwn.net \
--cc=darrick.wong@oracle.com \
--cc=dhowells@redhat.com \
--cc=dsterba@suse.com \
--cc=eguan@redhat.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jbacik@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=ross.zwisler@linux.intel.com \
--cc=tytso@mit.edu \
--cc=viro@ZenIV.linux.org.uk \
/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).