From: Mark Wielaard <mark@klomp.org>
To: Evgeny Vereshchagin <evvers@ya.ru>
Cc: david korczynski <david@adalogics.com>, elfutils-devel@sourceware.org
Subject: Re: Some fuzzer workarounds
Date: Mon, 21 Mar 2022 18:30:10 +0100 [thread overview]
Message-ID: <40bb3499abf806bc56500eb3c74374bff421afe0.camel@klomp.org> (raw)
In-Reply-To: <542296A2-061F-41F6-9BB2-92871407E80F@ya.ru>
Hi Evgeny,
On Mon, 2022-03-21 at 17:33 +0300, Evgeny Vereshchagin wrote:
> I tested the fuzz branch and I can confirm that all the issues
> reported by OSS-Fuzz found with ASan+UBSan are gone.
> I kind of lost track of them at some point but the following issues
> can no longer be triggered:
>
> fuzz-libdwfl-crashes/oss-fuzz-45629 \
> fuzz-libdwfl-crashes/oss-fuzz-45634 \
> fuzz-libdwfl-crashes/oss-fuzz-45635 \
> fuzz-libdwfl-crashes/oss-fuzz-45636 \
> fuzz-libdwfl-crashes/oss-fuzz-45646 \
> fuzz-libelf-crashes/oss-fuzz-45637 \
> fuzz-libelf-crashes/oss-fuzz-45682
Great. Thanks for testing. All patches from the fuzz branch are now
merged. My local fuzzer also hasn't found any new issues for almost 24
hours now.
> The unit tests have nothing to do with the fuzz branch because once I
> pointed the tests to the master branch they also
> failed. Looking at "phdr[8]: unknown object file note type 3405650558
> with owner name 'FDO' at offset 200" it seems
> it's caused by the toolchain used there. On Fedora 35 the tests pass.
Ah, oops. Yeah that is:
https://systemd.io/COREDUMP_PACKAGE_METADATA/
https://fedoraproject.org/wiki/Changes/Package_information_on_ELF_objects
There are actually patches to properly recognize those.
https://sourceware.org/pipermail/elfutils-devel/2021q4/thread.html#4375
I'll integrate those asap.
Cheers,
Mark
next prev parent reply other threads:[~2022-03-21 17:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 13:30 Mark Wielaard
2022-03-17 13:30 ` [PATCH 1/2] libelf: Take map offset into account for Shdr alignment check in elf_begin Mark Wielaard
2022-03-17 13:30 ` [PATCH 2/2] libelf: Make sure ar_size starts with a digit before calling atol Mark Wielaard
2022-03-18 9:11 ` Evgeny Vereshchagin
2022-03-18 11:44 ` Mark Wielaard
2022-03-18 13:18 ` Evgeny Vereshchagin
2022-03-18 7:26 ` Some fuzzer workarounds Evgeny Vereshchagin
2022-03-19 11:08 ` Evgeny Vereshchagin
2022-03-21 2:24 ` Evgeny Vereshchagin
2022-03-21 10:50 ` Mark Wielaard
2022-03-21 11:10 ` Evgeny Vereshchagin
2022-03-21 14:33 ` Evgeny Vereshchagin
2022-03-21 17:30 ` Mark Wielaard [this message]
2022-03-21 18:01 ` Evgeny Vereshchagin
2022-03-22 16:59 ` Evgeny Vereshchagin
2022-03-23 0:35 ` Mark Wielaard
2022-03-23 1:15 ` Evgeny Vereshchagin
2022-03-23 9:21 ` Mark Wielaard
2022-03-21 10:57 ` Mark Wielaard
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=40bb3499abf806bc56500eb3c74374bff421afe0.camel@klomp.org \
--to=mark@klomp.org \
--cc=david@adalogics.com \
--cc=elfutils-devel@sourceware.org \
--cc=evvers@ya.ru \
/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).