qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Darren Kenny <darren.kenny@oracle.com>
To: Alexander Bulekov <alxndr@bu.edu>, qemu-devel@nongnu.org
Cc: "Laurent Vivier" <lvivier@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Alexander Bulekov" <alxndr@bu.edu>,
	"Bandan Das" <bsd@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH] fuzz: avoid double-fetches by default
Date: Thu, 03 Dec 2020 14:27:08 +0000	[thread overview]
Message-ID: <m2k0tz55j7.fsf@oracle.com> (raw)
In-Reply-To: <20201202164214.93867-1-alxndr@bu.edu>

On Wednesday, 2020-12-02 at 11:42:14 -05, Alexander Bulekov wrote:
> The generic fuzzer can find double-fetch bugs. However:
> * We currently have no good way of producing qemu-system reproducers for
>   double-fetch bugs. Even if we can get developers to run the binary-blob
>   reproducers with the qemu-fuzz builds, we currently don't have a minimizer for
>   these reproducers, so they are usually not easy to follow.
> * Often times the fuzzer will provide a reproducer containing a
>   double-fetch for a bug that can be reproduced without double-fetching.
>
> Until we find a way to build nice double-fetch reproducers that
> developers are willing to look at, lets tell OSS-Fuzz to avoid
> double-fetches.
>
> Signed-off-by: Alexander Bulekov <alxndr@bu.edu>

Reviewed-by: Darren Kenny <darren.kenny@oracle.com>

> ---
>  tests/qtest/fuzz/generic_fuzz.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/tests/qtest/fuzz/generic_fuzz.c b/tests/qtest/fuzz/generic_fuzz.c
> index 262a963d2e..07ad690683 100644
> --- a/tests/qtest/fuzz/generic_fuzz.c
> +++ b/tests/qtest/fuzz/generic_fuzz.c
> @@ -916,6 +916,7 @@ static GString *generic_fuzz_predefined_config_cmdline(FuzzTarget *t)
>      g_assert(t->opaque);
>  
>      config = t->opaque;
> +    setenv("QEMU_AVOID_DOUBLE_FETCH", "1", 1);
>      setenv("QEMU_FUZZ_ARGS", config->args, 1);
>      setenv("QEMU_FUZZ_OBJECTS", config->objects, 1);
>      return generic_fuzz_cmdline(t);
> -- 
> 2.28.0


      reply	other threads:[~2020-12-03 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 16:42 [PATCH] fuzz: avoid double-fetches by default Alexander Bulekov
2020-12-03 14:27 ` Darren Kenny [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=m2k0tz55j7.fsf@oracle.com \
    --to=darren.kenny@oracle.com \
    --cc=alxndr@bu.edu \
    --cc=bsd@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --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).