From: Kent Overstreet <kent.overstreet@linux.dev>
To: Dave Chinner <david@fromorbit.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Mikulas Patocka <mpatocka@redhat.com>,
linux-bcachefs@vger.kernel.org, dm-devel@redhat.com,
linux-fsdevel@vger.kernel.org
Subject: Re: fuzzing bcachefs with dm-flakey
Date: Mon, 29 May 2023 19:51:21 -0400 [thread overview]
Message-ID: <ZHU6eX2wOXJjDVc0@moria.home.lan> (raw)
In-Reply-To: <ZHUxbLh1P9yiq2c9@dread.disaster.area>
On Tue, May 30, 2023 at 09:12:44AM +1000, Dave Chinner wrote:
> Perhaps it is worthwhile running the same tests on btrfs so we can
> something to compare the bcachefs behaviour to. I suspect that btrfs
> will fair little better on the single device, no checksums
> corruption test....
It's also a test we _should_ be doing much, much better on: we've got
validation code for every key type that we run on every metadata read,
so there's no excuses for thees bugs and they will be fixed.
Just a question of when and in what order...
next prev parent reply other threads:[~2023-05-29 23:51 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 [this message]
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
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=ZHU6eX2wOXJjDVc0@moria.home.lan \
--to=kent.overstreet@linux.dev \
--cc=david@fromorbit.com \
--cc=dm-devel@redhat.com \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).