From: Vijay Chidambaram <vijay@cs.utexas.edu>
To: Filipe Manana <fdmanana@kernel.org>
Cc: fstests <fstests@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] fstests: generic, fsync fuzz tester with fsstress
Date: Wed, 15 May 2019 10:07:14 -0500 [thread overview]
Message-ID: <CAHWVdUWQXDf0fDTg=43ySNEbTEqPh1ue6ZujsBX-wTsmLQGz3A@mail.gmail.com> (raw)
In-Reply-To: <20190515150221.16647-1-fdmanana@kernel.org>
On Wed, May 15, 2019 at 10:02 AM <fdmanana@kernel.org> wrote:
>
> From: Filipe Manana <fdmanana@suse.com>
>
> Run fsstress, fsync every file and directory, simulate a power failure and
> then verify the all files and directories exist, with the same data and
> metadata they had before the power failure.
I'm happy to see this sort of crash testing be merged into the Linux
kernel! I think something like this being run after every
merge/nightly build will make file systems significantly more robust
to crash-recovery bugs.
next prev parent reply other threads:[~2019-05-15 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 15:02 [PATCH] fstests: generic, fsync fuzz tester with fsstress fdmanana
2019-05-15 15:07 ` Vijay Chidambaram [this message]
2019-05-16 8:09 ` Johannes Thumshirn
2019-05-16 9:28 ` Theodore Ts'o
2019-05-16 9:54 ` Filipe Manana
2019-05-16 9:54 ` Filipe Manana
2019-05-16 16:59 ` Theodore Ts'o
2019-05-16 17:18 ` Filipe Manana
2019-05-17 15:33 ` Filipe Manana
2019-05-17 3:42 ` Eryu Guan
2019-05-17 15:34 ` [PATCH v2] " fdmanana
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='CAHWVdUWQXDf0fDTg=43ySNEbTEqPh1ue6ZujsBX-wTsmLQGz3A@mail.gmail.com' \
--to=vijay@cs.utexas.edu \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@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.