From: Alexander Cherepanov <cherepan@mccme.ru>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: Fuzzing elfutils
Date: Mon, 22 Dec 2014 01:20:24 +0300 [thread overview]
Message-ID: <549747A8.3020804@mccme.ru> (raw)
In-Reply-To: 1418947995.19814.11.camel@bordewijk.wildebeest.org
[-- Attachment #1: Type: text/plain, Size: 2344 bytes --]
On 2014-12-19 03:13, Mark Wielaard wrote:
> On Thu, 2014-12-18 at 21:15 +0300, Alexander Cherepanov wrote:
>>> Thanks. I'll try to reproduce them soon. But without a general leb128
>>> length check fix using eu-readelf -w might be somewhat unreliable (and
>>> this also might impact -e/--exceptions).
>>
>> There are many patches flowing and it's not clear which are relevant for
>> my crashes and when it's the right time to start fuzzing again.
>
> Now would be a good time :)
Ok:-)
> I am not aware of any pending crashers.
> Although I am aware of 3 areas that still need some work because they
> could potentially cause crashes on bad input (I'll update the bug soon).
It seems the crashes I uploaded yesterday hit at least one of these
areas (Dwarf_Abbrev) but maybe not others. OTOH you don't need fuzzing
to hit these areas if you already know they are problematic. Fuzzing is
more interesting when it uncovers something unexpected.
> Sorry there were so many changes. But sadly there were a lot of
> crashers. I hope we got them all. And some of yours needed some more
> general fixes that needed some discussion. But those patches are now
> finally all in.
The amount of fixes is not something to be sorry about, it's something
to be proud of:-)
But it would be nice to have an idea which commits fix which crashes.
Your first commit (d0070a9) included Reported-by: -- thanks! But it was
the only such commit, then it was not clear whether you fix further
crashes from the same bunch or fix completely different crashes.
I guess I can formulate two wishes now:
- to include Reported-by: tag in your commits (to make it possible to
track progress and as a credit);
- to let me know when it's reasonable to start next round of fuzzing.
[skip]
>> Further fuzzing found 3 crashes in readelf. Not sure if you want to look
>> into them now.
>
> Yes, please do add them to the "fuzzer crash bug":
> https://bugzilla.redhat.com/show_bug.cgi?id=1170810
Done.
> Sorry if they don't get immediately fixed for 0.161. But the release
> should already have happened and I like to include just some testsuite
> cleanups and get it shipped, before continuing with more work.
Sure, trying to fix everything will postpone the release indefinitely:-(
--
Alexander Cherepanov
next reply other threads:[~2014-12-21 22:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 22:20 Alexander Cherepanov [this message]
[not found] <199C1200-40AC-4AD2-89D4-24E172CBA353@catenacyber.fr>
2022-10-21 12:58 ` Philippe Antoine
2022-10-21 13:22 ` Frank Ch. Eigler
2022-10-21 19:57 ` Evgeny Vereshchagin
2022-10-22 9:27 ` Philippe Antoine
2022-10-22 10:21 ` Evgeny Vereshchagin
2022-10-21 13:33 ` Evgeny Vereshchagin
-- strict thread matches above, loose matches on Subject: below --
2014-12-31 11:03 Mark Wielaard
2014-12-29 3:16 Alexander Cherepanov
2014-12-23 11:42 Mark Wielaard
2014-12-19 0:13 Mark Wielaard
2014-12-18 18:15 Alexander Cherepanov
2014-12-12 12:08 Mark Wielaard
2014-12-08 9:14 Mark Wielaard
2014-12-08 8:52 Mark Wielaard
2014-12-08 3:06 Alexander Cherepanov
2014-12-08 1:01 Alexander Cherepanov
2014-12-05 8:58 Mark Wielaard
2014-12-04 23:10 Alexander Cherepanov
2014-12-04 16:03 Mark Wielaard
2014-12-04 14:27 Mark Wielaard
2014-12-03 15:16 Alexander Cherepanov
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=549747A8.3020804@mccme.ru \
--to=cherepan@mccme.ru \
--cc=elfutils-devel@lists.fedorahosted.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 read-only IMAP folder(s) and NNTP newsgroup(s).