From: Dima Stepanov <dimastep@yandex-team.ru>
To: Thomas Huth <thuth@redhat.com>
Cc: stefanha@gmail.com, alxndr@bu.edu, qemu-devel@nongnu.org,
yc-core@yandex-team.ru, darren.kenny@oracle.com
Subject: Re: [PATCH v2 1/2] fuzz: add virtio-blk fuzz target
Date: Fri, 13 Nov 2020 13:10:20 +0300 [thread overview]
Message-ID: <20201113101020.GA7758@dimastep-nix> (raw)
In-Reply-To: <ab97459c-f0e4-5f0d-455a-362001cca6ba@redhat.com>
On Mon, Nov 09, 2020 at 01:24:20PM +0100, Thomas Huth wrote:
> On 09/11/2020 12.25, Dima Stepanov wrote:
> > The virtio-blk fuzz target sets up and fuzzes the available virtio-blk
> > queues. The implementation is based on two files:
> > - tests/qtest/fuzz/virtio_scsi_fuzz.c
> > - tests/qtest/virtio_blk_test.c
> >
> > Signed-off-by: Dima Stepanov <dimastep@yandex-team.ru>
> > Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
> > ---
> > tests/qtest/fuzz/meson.build | 1 +
> > tests/qtest/fuzz/virtio_blk_fuzz.c | 234 +++++++++++++++++++++++++++++++++++++
> > 2 files changed, 235 insertions(+)
> > create mode 100644 tests/qtest/fuzz/virtio_blk_fuzz.c
>
> Thanks, I can add this to my next qtest-related pull request.
> Note: I just spotted your patch by accident ... please put me on CC: if you
> want me to merge qtest/fuzzer related patches.
Hi Thomas,
Thanks for handling it. Got it! Will add you to CC for the next fuzzing
pull requests.
Dima.
>
> Thomas
>
next prev parent reply other threads:[~2020-11-13 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 11:25 [PATCH v2 0/2] fuzz: add virtio-blk fuzz target Dima Stepanov
2020-11-09 11:25 ` [PATCH v2 1/2] " Dima Stepanov
2020-11-09 12:24 ` Thomas Huth
2020-11-13 10:10 ` Dima Stepanov [this message]
2020-11-09 11:25 ` [PATCH v2 2/2] docs/fuzz: update make and run command lines Dima Stepanov
2020-11-09 12:20 ` Thomas Huth
2020-11-09 14:45 ` Alexander Bulekov
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=20201113101020.GA7758@dimastep-nix \
--to=dimastep@yandex-team.ru \
--cc=alxndr@bu.edu \
--cc=darren.kenny@oracle.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=thuth@redhat.com \
--cc=yc-core@yandex-team.ru \
/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).