Messages in this thread | | | From | Jeff Layton <> | Subject | [xfstests PATCH v3 0/5] add a test for reporting writeback errors across all fds on fsync | Date | Wed, 31 May 2017 09:08:15 -0400 |
| |
This patchset is a companion to the Linux kernel patch series I recently posted with the cover letter:
[PATCH v5 00/17] fs: introduce new writeback error reporting and convert ext2 and ext4 to use it
That patchset adds a new userland-visible change to report errors on all open file descriptions when there is an error on fsync, not just the first one to race in.
Note that this set contains a patch to emulate $SCRATCH_LOGDEV on btrfs, but the kernel patches for that are not quite ready yet. The test did pass on btrfs in an earlier incarnation of the set, however.
Jeff Layton (5): generic: add a writeback error handling test ext4: allow ext4 to use $SCRATCH_LOGDEV generic: test writeback error handling on dmerror devices ext3: allow it to put journal on a separate device when doing scratch_mkfs btrfs: allow it to use $SCRATCH_LOGDEV
common/dmerror | 13 ++-- common/rc | 16 ++++- doc/auxiliary-programs.txt | 8 +++ src/Makefile | 2 +- src/fsync-err.c | 161 +++++++++++++++++++++++++++++++++++++++++++++ tests/generic/998 | 64 ++++++++++++++++++ tests/generic/998.out | 2 + tests/generic/999 | 76 +++++++++++++++++++++ tests/generic/999.out | 3 + tests/generic/group | 2 + tools/dmerror | 44 +++++++++++++ 11 files changed, 384 insertions(+), 7 deletions(-) create mode 100644 src/fsync-err.c 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 create mode 100755 tools/dmerror
-- 2.9.4
| |