From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Bulekov <alxndr@bu.edu>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
Thomas Huth <thuth@redhat.com>,
f4bug@amsat.org, darren.kenny@oracle.com, bsd@redhat.com,
stefanha@redhat.com, dimastep@yandex-team.ru
Subject: Re: [PATCH v5 02/16] fuzz: Add general virtual-device fuzzer
Date: Wed, 21 Oct 2020 14:44:50 +0200 [thread overview]
Message-ID: <675e45e4-3de1-bf0a-b7d3-117710b7fba2@redhat.com> (raw)
In-Reply-To: <20201021010752.973230-3-alxndr@bu.edu>
On 21/10/20 03:07, Alexander Bulekov wrote:
> +static GString *generic_fuzz_cmdline(FuzzTarget *t)
^^^^^^^
> +{
> + GString *cmd_line = g_string_new(TARGET_NAME);
> + if (!getenv("QEMU_FUZZ_ARGS")) {
> + usage();
> + }
> + g_string_append_printf(cmd_line, " -display none \
> + -machine accel=qtest, \
> + -m 512M %s ", getenv("QEMU_FUZZ_ARGS"));
> + return cmd_line;
> +}
> +
> +static void register_generic_fuzz_targets(void)
> +{
> + fuzz_add_target(&(FuzzTarget){
> + .name = "generic-fuzz",
> + .description = "Fuzz based on any qemu command-line args. ",
> + .get_init_cmdline = general_fuzz_cmdline,
^^^^^^^
Does this actually compile?
Paolo
> + .pre_fuzz = general_pre_fuzz,
> + .fuzz = general_fuzz});
next prev parent reply other threads:[~2020-10-21 12:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 1:07 [PATCH v5 00/16] Add a Generic Virtual Device Fuzzer Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 01/16] memory: Add FlatView foreach function Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 02/16] fuzz: Add general virtual-device fuzzer Alexander Bulekov
2020-10-21 12:44 ` Paolo Bonzini [this message]
2020-10-21 14:49 ` Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 03/16] fuzz: Add PCI features to the general fuzzer Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 04/16] fuzz: Add DMA support to the generic-fuzzer Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 05/16] fuzz: Declare DMA Read callback function Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 06/16] fuzz: Add fuzzer callbacks to DMA-read functions Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 07/16] fuzz: Add support for custom crossover functions Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 08/16] fuzz: add a DISABLE_PCI op to general-fuzzer Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 09/16] fuzz: add a crossover function to generic-fuzzer Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 10/16] scripts/oss-fuzz: Add script to reorder a general-fuzzer trace Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 11/16] scripts/oss-fuzz: Add crash trace minimization script Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 12/16] fuzz: Add instructions for using general-fuzz Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 13/16] fuzz: add an "opaque" to the FuzzTarget struct Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 14/16] fuzz: add general-fuzz configs for oss-fuzz Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 15/16] fuzz: register predefined general-fuzz configs Alexander Bulekov
2020-10-21 1:07 ` [PATCH v5 16/16] scripts/oss-fuzz: remove the general-fuzz target Alexander Bulekov
2020-10-21 13:24 ` [PATCH v5 00/16] Add a Generic Virtual Device Fuzzer 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=675e45e4-3de1-bf0a-b7d3-117710b7fba2@redhat.com \
--to=pbonzini@redhat.com \
--cc=alxndr@bu.edu \
--cc=bsd@redhat.com \
--cc=darren.kenny@oracle.com \
--cc=dimastep@yandex-team.ru \
--cc=f4bug@amsat.org \
--cc=lvivier@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).