From: Shentino <shentino@gmail.com>
To: dave@jikos.cz, Shentino <shentino@gmail.com>,
Michael <mike@draftx.net>, cwillu <cwillu@cwillu.com>,
linux-btrfs@vger.kernel.org
Subject: Re: rfc: fuzz testing by direct writes to device
Date: Wed, 5 Sep 2012 14:23:11 -0700 [thread overview]
Message-ID: <CAGDaZ_qDF31tLfKLKCWDSH33yBoqucMQGpAM_9h7kb1bGz-1qw@mail.gmail.com> (raw)
In-Reply-To: <20120905150402.GK17430@twin.jikos.cz>
On Wed, Sep 5, 2012 at 8:04 AM, David Sterba <dave@jikos.cz> wrote:
> On Sun, Sep 02, 2012 at 04:43:48AM -0700, Shentino wrote:
>> I assume the same results are expected during a scrub as during a normal read?
>
> yes
>
>> > I've tested this on an 2 disk data/raid1, metadata/raid1 with a running
>> > dd over one of the devices continually and using the filesystem. It was
>> > slower.
>>
>> Would I be correct to assume that a core dump on fsck is an automatic
>> bug or is using the old 3.3.8 kernel a taint that would invalidate a
>> report? Note that this is for the btrfs-progs containing the fsck,
>> not the actual kernel side code.
>
> You're talking about fsck and kernel, I'm not quite sure which one do
> you refer to with 'bug'.
>
> fsck can crash when it finds unexpected data in the tree structures,
> but this would mean that it passed through the checksum verification
> earlier. This would be a bug, and if it is reproducible on newer kernels
> a report on 3.3.x does not disqualify it right away.
>
> Same holds for kernel, a datastructure inconsistency will most probably
> lead to a BUG and subsequent crash.
>
> david
By this I mean running fsck on a btrfs that was trashed by a 3.3.8 kernel bug.
next prev parent reply other threads:[~2012-09-05 21:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 6:44 rfc: fuzz testing by direct writes to device Shentino
2012-09-01 8:10 ` Shentino
2012-09-01 15:41 ` Michael
2012-09-01 17:23 ` Shentino
2012-09-01 20:59 ` cwillu
2012-09-01 22:31 ` Shentino
2012-09-01 23:49 ` Michael
2012-09-02 1:03 ` Shentino
2012-09-02 5:44 ` David Sterba
2012-09-02 11:43 ` Shentino
2012-09-05 15:04 ` David Sterba
2012-09-05 21:23 ` Shentino [this message]
2012-09-04 18:15 ` Goffredo Baroncelli
2012-09-05 1:59 ` Shentino
2012-09-05 5:46 ` Goffredo Baroncelli
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=CAGDaZ_qDF31tLfKLKCWDSH33yBoqucMQGpAM_9h7kb1bGz-1qw@mail.gmail.com \
--to=shentino@gmail.com \
--cc=cwillu@cwillu.com \
--cc=dave@jikos.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=mike@draftx.net \
/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).