From: Amir Goldstein <amir73il@gmail.com>
To: Eryu Guan <eguan@redhat.com>
Cc: Josef Bacik <jbacik@fb.com>,
fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH v4 0/8] Crash consistency xfstest using dm-log-writes
Date: Thu, 7 Sep 2017 13:03:05 +0300 [thread overview]
Message-ID: <1504778593-12071-1-git-send-email-amir73il@gmail.com> (raw)
Eryu,
These are the rest of the patches following the fsx patches
v4 posting.
There are no changes to the replay-log patches since v3.
The test patches address your v3 review comments.
The status of tests in current upstream:
- 500 fails sometimes on btrfs/ext4/xfs
- 501 fails always on ext4
- 502 fails sometimes on xfs
- 503 fails always on xfs
The data loss issue found by test 500 on xfs is fixed by
commit 47c7d0b19502 ("xfs: fix incorrect log_flushed on fsync")
now in master.
Amir.
Amir Goldstein (8):
log-writes: add replay-log program to replay dm-log-writes target
replay-log: add validations for corrupt log entries
replay-log: add support for replaying ops in target device sector
fstests: add support for working with dm-log-writes target
fstests: crash consistency fsx test using dm-log-writes
fstests: regression test for ext4 crash consistency bug
fstests: crash consistency fsx test for cloned files
fstests: regression test for xfs leftover CoW extent error
.gitignore | 1 +
README | 2 +
common/dmlogwrites | 90 +++++++++
doc/auxiliary-programs.txt | 8 +
doc/requirement-checking.txt | 20 ++
src/Makefile | 2 +-
src/log-writes/Makefile | 23 +++
src/log-writes/SOURCE | 6 +
src/log-writes/log-writes.c | 458 +++++++++++++++++++++++++++++++++++++++++++
src/log-writes/log-writes.h | 81 ++++++++
src/log-writes/replay-log.c | 389 ++++++++++++++++++++++++++++++++++++
tests/generic/500 | 138 +++++++++++++
tests/generic/500.out | 2 +
tests/generic/501 | 80 ++++++++
tests/generic/501.out | 2 +
tests/generic/502 | 141 +++++++++++++
tests/generic/502.out | 2 +
tests/generic/503 | 74 +++++++
tests/generic/503.out | 2 +
tests/generic/group | 4 +
20 files changed, 1524 insertions(+), 1 deletion(-)
create mode 100644 common/dmlogwrites
create mode 100644 src/log-writes/Makefile
create mode 100644 src/log-writes/SOURCE
create mode 100644 src/log-writes/log-writes.c
create mode 100644 src/log-writes/log-writes.h
create mode 100644 src/log-writes/replay-log.c
create mode 100755 tests/generic/500
create mode 100644 tests/generic/500.out
create mode 100755 tests/generic/501
create mode 100644 tests/generic/501.out
create mode 100755 tests/generic/502
create mode 100644 tests/generic/502.out
create mode 100755 tests/generic/503
create mode 100644 tests/generic/503.out
--
2.7.4
next reply other threads:[~2017-09-07 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 10:03 Amir Goldstein [this message]
2017-09-07 10:03 ` [PATCH v4 1/8] log-writes: add replay-log program to replay dm-log-writes target Amir Goldstein
2017-09-09 10:22 ` Eryu Guan
2017-09-07 10:03 ` [PATCH v4 2/8] replay-log: add validations for corrupt log entries Amir Goldstein
2017-09-07 10:03 ` [PATCH v4 3/8] replay-log: add support for replaying ops in target device sector range Amir Goldstein
2017-09-07 10:03 ` [PATCH v4 4/8] fstests: add support for working with dm-log-writes target Amir Goldstein
2017-09-07 10:03 ` [PATCH v4 5/8] fstests: crash consistency fsx test using dm-log-writes Amir Goldstein
2017-09-07 10:03 ` [PATCH v4 6/8] fstests: regression test for ext4 crash consistency bug Amir Goldstein
2017-09-07 10:03 ` [PATCH v4 7/8] fstests: crash consistency fsx test for cloned files Amir Goldstein
2017-09-07 10:03 ` [PATCH v4 8/8] fstests: regression test for xfs leftover CoW extent error Amir Goldstein
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=1504778593-12071-1-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=jbacik@fb.com \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.