From: David Sterba <dsterba@suse.cz>
To: Lukas Lueg <lukas.lueg@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Multiple bugs found by fuzzing BTRFS
Date: Tue, 30 Aug 2016 13:09:55 +0200 [thread overview]
Message-ID: <20160830110955.GA16983@suse.cz> (raw)
In-Reply-To: <CAJF-kYkQv11XCzcMfP02yw2AnO4LssbVDLuTqzZqB9ddeCCaow@mail.gmail.com>
On Mon, Aug 29, 2016 at 08:47:10PM +0200, Lukas Lueg wrote:
> I'll report new issues to bz as they turn up from the current round
> only if they represent a yet unreported kind of problem (e.g. there
> are stack-based buffer over- and underruns lurking, I lost them due to
> a bug in my setup, though). The next round will be much faster as I've
> now vastly improved my automatic bug triage and fuzzing speed.
>
> I lost interest once after bugs went unanswered - there are bugs still
> open and unanswered from 2015/04. I hope this won't be a problem this
> time.
Yeah, the lack if replies is unfortunate and happens. There's a
disproportion between number of people who report bugs and who go
through them and fix. I personally look out for the fuzzing bugs as
they usually come with an image and it's easy to create a testcase from
them, reproducible bugs also tend to get fixes faster.
I must have missed the bugs though, there are 3 fuzzed images, reported
by you in bugs 96971, 97191 and 97271. I see two more (97031 and 97021)
and will look into them.
prev parent reply other threads:[~2016-08-30 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 6:06 Multiple bugs found by fuzzing BTRFS Lukas Lueg
2016-08-29 6:20 ` Qu Wenruo
2016-08-29 6:56 ` Lukas Lueg
2016-08-29 17:02 ` David Sterba
2016-08-29 18:47 ` Lukas Lueg
2016-08-30 11:09 ` David Sterba [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=20160830110955.GA16983@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lukas.lueg@gmail.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 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.