From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v4 0/5] fsx additions for crash consistency tests
Date: Thu, 7 Sep 2017 15:58:51 +0800 [thread overview]
Message-ID: <20170907075851.GQ8034@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1504769198-4921-1-git-send-email-amir73il@gmail.com>
On Thu, Sep 07, 2017 at 10:26:33AM +0300, Amir Goldstein wrote:
> Eryu,
>
> This is a re-post of v3 fsx patches with a correction to
> the 2nd patch which introduces -j <logid>.
Thanks a lot for the repost! I plan to pull this log-writes work in this
week after my minor nits to the previous patchset are addressed, if
there're no more review comments/complains from other reviewers.
Thanks,
Eryu
>
> Amir.
>
> Amir Goldstein (5):
> fsx: add support for integrity check with dm-log-writes target
> fsx: add optional logid prefix to log messages
> fsx: add support for recording operations to a file
> fsx: add support for writing constant instead of random data
> fsx: add support for keeping existing file
>
> ltp/fsx.c | 274 ++++++++++++++++++++++++++++++++++++++++++++++++--------------
> 1 file changed, 214 insertions(+), 60 deletions(-)
>
> --
> 2.7.4
>
prev parent reply other threads:[~2017-09-07 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 7:26 [PATCH v4 0/5] fsx additions for crash consistency tests Amir Goldstein
2017-09-07 7:26 ` [PATCH v4 1/5] fsx: add support for integrity check with dm-log-writes target Amir Goldstein
2017-09-07 7:26 ` [PATCH v4 2/5] fsx: add optional logid prefix to log messages Amir Goldstein
2017-09-07 7:26 ` [PATCH v4 3/5] fsx: add support for recording operations to a file Amir Goldstein
2017-09-07 7:26 ` [PATCH v4 4/5] fsx: add support for writing constant instead of random data Amir Goldstein
2017-09-07 7:26 ` [PATCH v4 5/5] fsx: add support for keeping existing file Amir Goldstein
2017-09-07 12:38 ` Amir Goldstein
2017-09-07 14:06 ` Eryu Guan
2017-09-07 7:58 ` Eryu Guan [this message]
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=20170907075851.GQ8034@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=amir73il@gmail.com \
--cc=fstests@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