From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Bulekov <alxndr@bu.edu>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, thuth@redhat.com,
Li Qiang <liq3ea@163.com>,
f4bug@amsat.org
Subject: Re: [PATCH v2] configure: fix --enable-fuzzing linker failures
Date: Mon, 22 Feb 2021 15:10:08 +0100 [thread overview]
Message-ID: <8b32dd12-826f-77c9-f68d-40151d61d783@redhat.com> (raw)
In-Reply-To: <20210221174510.22542-1-alxndr@bu.edu>
On 21/02/21 18:45, Alexander Bulekov wrote:
> With --enable-fuzzing, QEMU_CFLAGS include -fsanitize=fuzzer-no-link.
> This should allow us to build non-fuzzer binaries using objects
> instrumented for fuzzing. However, to do that, we also need to link with
> -fsanitize=fuzzer-no-link. We were not doing that.
>
> Reported-by: Li Qiang <liq3ea@163.com>,
> Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
> ---
> v2: Fix a mistake in the added QEMU_LDFLAGS line
>
> configure | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/configure b/configure
> index a79b3746d4..19f2b88589 100755
> --- a/configure
> +++ b/configure
> @@ -6096,7 +6096,17 @@ if test "$fuzzing" = "yes" ; then
> # If LIB_FUZZING_ENGINE is set, assume we are running on OSS-Fuzz, and the
> # needed CFLAGS have already been provided
> if test -z "${LIB_FUZZING_ENGINE+xxx}" ; then
> + # Add CFLAGS to tell clang to add fuzzer-related instrumentation to all the
> + # compiled code.
> QEMU_CFLAGS="$QEMU_CFLAGS -fsanitize=fuzzer-no-link"
> + # To build non-fuzzer binaries with --enable-fuzzing, link everything with
> + # fsanitize=fuzzer-no-link. Otherwise, the linker will be unable to bind
> + # the fuzzer-related callbacks added by instrumentation.
> + QEMU_LDFLAGS="$QEMU_LDFLAGS -fsanitize=fuzzer-no-link"
> + # For the actual fuzzer binaries, we need to link against the libfuzzer
> + # library. Provide the flags for doing this in FUZZ_EXE_LDFLAGS. The meson
> + # rule for the fuzzer adds these to the link_args. They need to be
> + # configurable, to support OSS-Fuzz
> FUZZ_EXE_LDFLAGS="-fsanitize=fuzzer"
> else
> FUZZ_EXE_LDFLAGS="$LIB_FUZZING_ENGINE"
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2021-02-22 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 17:45 [PATCH v2] configure: fix --enable-fuzzing linker failures Alexander Bulekov
2021-02-22 5:44 ` Thomas Huth
2021-02-22 13:52 ` Li Qiang
2021-02-22 14:10 ` Paolo Bonzini [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=8b32dd12-826f-77c9-f68d-40151d61d783@redhat.com \
--to=pbonzini@redhat.com \
--cc=alxndr@bu.edu \
--cc=f4bug@amsat.org \
--cc=liq3ea@163.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).