From: "Darrick J. Wong" <djwong@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
linux-bcachefs@vger.kernel.org, dm-devel@redhat.com,
linux-fsdevel@vger.kernel.org
Subject: Re: fuzzing bcachefs with dm-flakey
Date: Fri, 9 Jun 2023 12:38:52 -0700 [thread overview]
Message-ID: <20230609193852.GI72224@frogsfrogsfrogs> (raw)
In-Reply-To: <7bf96e58-7151-a63d-317f-1ddedd4927ad@redhat.com>
On Fri, Jun 09, 2023 at 08:56:37PM +0200, Mikulas Patocka wrote:
>
>
> On Thu, 1 Jun 2023, Darrick J. Wong wrote:
>
> > On Mon, May 29, 2023 at 04:59:40PM -0400, Mikulas Patocka wrote:
> >
> > > #!/bin/sh -ex
> > > umount /mnt/test || true
> > > dmsetup remove_all || true
> > > rmmod brd || true
> > > SRC=/usr/src/git/bcachefs-tools
> > > while true; do
> > > modprobe brd rd_size=1048576
> > > bcachefs format --replicas=2 /dev/ram0 /dev/ram1
> > > dmsetup create flakey --table "0 `blockdev --getsize /dev/ram0` linear /dev/ram0 0"
> > > mount -t bcachefs /dev/mapper/flakey:/dev/ram1 /mnt/test
> > > dmsetup load flakey --table "0 `blockdev --getsize /dev/ram0` flakey /dev/ram0 0 0 1 4 random_write_corrupt 100000000 random_read_corrupt 100000000"
> >
> > Hey, that's really neat!
> >
> > Any chance you'd be willing to get the dm-flakey changes merged into
> > upstream so that someone can write a recoveryloop fstest to test all the
> > filesystems systematically?
> >
> > :D
> >
> > --D
>
> Yes, we will merge improved dm-flakey in the next merge window.
Thank you!
--D
> Mikulas
>
prev parent reply other threads:[~2023-06-09 19:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 20:59 fuzzing bcachefs with dm-flakey Mikulas Patocka
2023-05-29 21:14 ` Matthew Wilcox
2023-05-29 23:12 ` Dave Chinner
2023-05-29 23:51 ` Kent Overstreet
2023-05-30 12:23 ` Mikulas Patocka
2023-05-29 21:43 ` Kent Overstreet
2023-05-30 21:00 ` Mikulas Patocka
2023-05-30 23:29 ` Kent Overstreet
2023-06-09 20:57 ` Mikulas Patocka
2023-06-09 22:17 ` Kent Overstreet
2023-06-02 1:13 ` Darrick J. Wong
2023-06-09 18:56 ` Mikulas Patocka
2023-06-09 19:38 ` Darrick J. Wong [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=20230609193852.GI72224@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=dm-devel@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mpatocka@redhat.com \
/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).