From: Stefan Hajnoczi <stefanha@redhat.com>
To: Alexander Bulekov <alxndr@bu.edu>
Cc: darren.kenny@oracle.com, bsd@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/4] fuzz: misc changes for oss-fuzz compatability
Date: Tue, 26 May 2020 16:34:48 +0100 [thread overview]
Message-ID: <20200526153448.GA6797@stefanha-x1.localdomain> (raw)
In-Reply-To: <20200512030133.29896-1-alxndr@bu.edu>
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
On Mon, May 11, 2020 at 11:01:29PM -0400, Alexander Bulekov wrote:
> Hello,
> With these patches, the fuzzer passes the oss-fuzz build checks.
> There are also some miscelanous improvement to the fuzzer, in general:
> * If building for oss-fuzz, check executable_dir/pc-bios for
> the bios images
> * Fix a typo in the i440fx-qtest-reboot argument which resulted in an
> invalid argument to qemu_main
> * Add an alternate name to resolve libfuzzer's internal fuzzer::TPC
> object at link-time
> * For all fork-based fuzzers, run the main-loop in the parent, to
> prevent the clock from running far-ahead of the previous main-loop.
> -Alex
>
> Alexander Bulekov (4):
> fuzz: add datadir for oss-fuzz compatability
> fuzz: fix typo in i440fx-qtest-reboot arguments
> fuzz: add mangled object name to linker script
> fuzz: run the main-loop in fork-server process
>
> include/sysemu/sysemu.h | 2 ++
> softmmu/vl.c | 2 +-
> tests/qtest/fuzz/fork_fuzz.ld | 5 +++++
> tests/qtest/fuzz/fuzz.c | 15 +++++++++++++++
> tests/qtest/fuzz/i440fx_fuzz.c | 3 ++-
> tests/qtest/fuzz/virtio_net_fuzz.c | 2 ++
> tests/qtest/fuzz/virtio_scsi_fuzz.c | 2 ++
> 7 files changed, 29 insertions(+), 2 deletions(-)
>
> --
> 2.26.2
>
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-05-26 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 3:01 [PATCH 0/4] fuzz: misc changes for oss-fuzz compatability Alexander Bulekov
2020-05-12 3:01 ` [PATCH 1/4] fuzz: add datadir " Alexander Bulekov
2020-05-12 7:59 ` Darren Kenny
2020-05-20 16:51 ` Philippe Mathieu-Daudé
2020-05-20 18:07 ` Alexander Bulekov
2020-05-12 3:01 ` [PATCH 2/4] fuzz: fix typo in i440fx-qtest-reboot arguments Alexander Bulekov
2020-05-12 7:59 ` Darren Kenny
2020-05-12 8:14 ` Philippe Mathieu-Daudé
2020-05-12 3:01 ` [PATCH 3/4] fuzz: add mangled object name to linker script Alexander Bulekov
2020-05-12 8:01 ` Darren Kenny
2020-05-12 3:01 ` [PATCH 4/4] fuzz: run the main-loop in fork-server process Alexander Bulekov
2020-05-12 8:00 ` Darren Kenny
2020-05-19 15:47 ` [PATCH 0/4] fuzz: misc changes for oss-fuzz compatability Alexander Bulekov
2020-05-26 15:34 ` Stefan Hajnoczi [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=20200526153448.GA6797@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=alxndr@bu.edu \
--cc=bsd@redhat.com \
--cc=darren.kenny@oracle.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.