From: Aleksei Vetrov <vvvvvv@google.com>
To: Evgeny Vereshchagin <evverx@gmail.com>
Cc: Mark Wielaard <mark@klomp.org>, elfutils-devel@sourceware.org
Subject: Re: [PATCH 2/2] libdw: Use elf_rawdata when checking .debug section
Date: Tue, 21 Feb 2023 16:40:35 +0000 [thread overview]
Message-ID: <CAH2MdgqqVuwS-Qqo=8pWM6C0crrjQE=KHqoBwQYQaNRgGPNbAg@mail.gmail.com> (raw)
In-Reply-To: <CAKKs9uh1ci=EZKDC8AEO9hbV1YTAuJvkvBR13wBZegVe6sCKsw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
Hi Evgeny,
On Tue, Feb 21, 2023 at 2:29 AM Evgeny Vereshchagin <evverx@gmail.com>
wrote:
> Aleksei I wonder if it would be possible to add those fuzz targets to
> OSS-Fuzz? There are blind spots there and I think it would be really
great to
> start covering at least some of them.
We are fuzzing a tool named STG
(https://android.googlesource.com/platform/external/stg/+/refs/heads/master
),
which is using libdw and libdwfl from elfutils. And it already has support
for
execution through libFuzzer:
https://android.googlesource.com/platform/external/stg/+/refs/heads/master/fuzz/
The problem is in building infrastructure. STG as fuzzing target is built
inside
Google using internal build and fuzzing infrastructure, but in principle it
does
the same thing as OSS-Fuzz. An AOSP version of STG is built using Android
build
system, which doesn't support the same simplicity of building with
libFuzzer and
sanitizers. So it needs some work to integrate STG into OSS-Fuzz.
prev parent reply other threads:[~2023-02-21 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 15:55 Fix some .debug checking and gnu hash xlate logic Mark Wielaard
2023-02-20 15:55 ` [PATCH 1/2] libelf: memmove any extra bytes left by elf_cvt_gnuhash conversion Mark Wielaard
2023-02-20 15:55 ` [PATCH 2/2] libdw: Use elf_rawdata when checking .debug section Mark Wielaard
2023-02-20 16:02 ` Aleksei Vetrov
2023-02-21 2:28 ` Evgeny Vereshchagin
2023-02-21 11:24 ` Mark Wielaard
2023-02-23 10:20 ` Mark Wielaard
2023-02-21 16:40 ` Aleksei Vetrov [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='CAH2MdgqqVuwS-Qqo=8pWM6C0crrjQE=KHqoBwQYQaNRgGPNbAg@mail.gmail.com' \
--to=vvvvvv@google.com \
--cc=elfutils-devel@sourceware.org \
--cc=evverx@gmail.com \
--cc=mark@klomp.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).