From: Thomas Huth <thuth@redhat.com>
To: Alexander Bulekov <alxndr@bu.edu>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, Bandan Das <bsd@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Darren Kenny <darren.kenny@oracle.com>,
Qiuhao Li <Qiuhao.Li@outlook.com>
Subject: Re: [PATCH] fuzz: disable leak-detection for oss-fuzz builds
Date: Wed, 29 May 2024 08:01:11 +0200 [thread overview]
Message-ID: <c34f9009-65a4-4c9d-a99a-1633e8f6fe88@redhat.com> (raw)
In-Reply-To: <20240527150001.325565-1-alxndr@bu.edu>
On 27/05/2024 16.59, Alexander Bulekov wrote:
> When we are building for OSS-Fuzz, we want to ensure that the fuzzer
> targets are actually created, regardless of leaks. Leaks will be
> detected by the subsequent tests of the individual fuzz-targets.
>
> Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
> ---
> scripts/oss-fuzz/build.sh | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/scripts/oss-fuzz/build.sh b/scripts/oss-fuzz/build.sh
> index 5238f83343..7398298173 100755
> --- a/scripts/oss-fuzz/build.sh
> +++ b/scripts/oss-fuzz/build.sh
> @@ -92,6 +92,7 @@ make install DESTDIR=$DEST_DIR/qemu-bundle
> rm -rf $DEST_DIR/qemu-bundle/opt/qemu-oss-fuzz/bin
> rm -rf $DEST_DIR/qemu-bundle/opt/qemu-oss-fuzz/libexec
>
> +export ASAN_OPTIONS=detect_leaks=0
> targets=$(./qemu-fuzz-i386 | grep generic-fuzz | awk '$1 ~ /\*/ {print $2}')
> base_copy="$DEST_DIR/qemu-fuzz-i386-target-$(echo "$targets" | head -n 1)"
Would it maybe also make sense to check that $targets is not empty and error
out in case it is?
Thomas
next prev parent reply other threads:[~2024-05-29 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 14:59 [PATCH] fuzz: disable leak-detection for oss-fuzz builds Alexander Bulekov
2024-05-27 16:08 ` Philippe Mathieu-Daudé
2024-05-29 6:01 ` Thomas Huth [this message]
2024-05-29 7:43 ` Thomas Huth
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=c34f9009-65a4-4c9d-a99a-1633e8f6fe88@redhat.com \
--to=thuth@redhat.com \
--cc=Qiuhao.Li@outlook.com \
--cc=alxndr@bu.edu \
--cc=bsd@redhat.com \
--cc=darren.kenny@oracle.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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).