From: Peter Maydell <peter.maydell@linaro.org>
To: Alexander Bulekov <alxndr@bu.edu>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 00/10] Replace fork-based fuzzing with reboots
Date: Tue, 21 Feb 2023 13:14:24 +0000 [thread overview]
Message-ID: <CAFEAcA95TbfDPfncBqsoKTwJRFt+jryDL7qfaqt7f3PVcDgp6A@mail.gmail.com> (raw)
In-Reply-To: <20230217040855.16873-1-alxndr@bu.edu>
On Fri, 17 Feb 2023 at 04:09, Alexander Bulekov <alxndr@bu.edu> wrote:
>
> Hi Peter,
> The following changes since commit 6dffbe36af79e26a4d23f94a9a1c1201de99c261:
>
> Merge tag 'migration-20230215-pull-request' of https://gitlab.com/juan.quintela/qemu into staging (2023-02-16 13:09:51 +0000)
>
> are available in the Git repository at:
>
> https://gitlab.com/a1xndr/qemu/ tags/pr-2023-02-16
>
> for you to fetch changes up to 7d9e5f18a94792ed875a1caed2bfcd1e68a49481:
>
> docs/fuzz: remove mentions of fork-based fuzzing (2023-02-16 23:02:46 -0500)
>
> ----------------------------------------------------------------
> Replace fork-based fuzzing with reboots.
> Now the fuzzers will reboot the guest between inputs.
>
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/8.0
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2023-02-21 13:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 4:08 [PULL 00/10] Replace fork-based fuzzing with reboots Alexander Bulekov
2023-02-17 4:08 ` [PULL 01/10] hw/sparse-mem: clear memory on reset Alexander Bulekov
2023-02-17 4:08 ` [PULL 02/10] fuzz: add fuzz_reset API Alexander Bulekov
2023-02-17 10:48 ` Darren Kenny
2023-02-17 14:47 ` Alexander Bulekov
2023-02-17 4:08 ` [PULL 03/10] fuzz/generic-fuzz: use reboots instead of forks to reset state Alexander Bulekov
2023-02-17 4:08 ` [PULL 04/10] fuzz/generic-fuzz: add a limit on DMA bytes written Alexander Bulekov
2023-02-17 4:08 ` [PULL 05/10] fuzz/virtio-scsi: remove fork-based fuzzer Alexander Bulekov
2023-02-17 4:08 ` [PULL 06/10] fuzz/virtio-net: " Alexander Bulekov
2023-02-17 4:08 ` [PULL 07/10] fuzz/virtio-blk: " Alexander Bulekov
2023-02-17 4:08 ` [PULL 08/10] fuzz/i440fx: " Alexander Bulekov
2023-02-17 4:08 ` [PULL 09/10] fuzz: remove fork-fuzzing scaffolding Alexander Bulekov
2023-02-17 4:08 ` [PULL 10/10] docs/fuzz: remove mentions of fork-based fuzzing Alexander Bulekov
2023-02-21 13:14 ` Peter Maydell [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=CAFEAcA95TbfDPfncBqsoKTwJRFt+jryDL7qfaqt7f3PVcDgp6A@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alxndr@bu.edu \
--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 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).