From: Thomas Huth <thuth@redhat.com>
To: Alexander Bulekov <alxndr@bu.edu>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, Bandan Das <bsd@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH 1/2] docs/fuzz: fix pre-meson path
Date: Mon, 18 Jan 2021 08:50:05 +0100 [thread overview]
Message-ID: <d94da0a9-0b54-9b65-cc3e-4232e51f1cab@redhat.com> (raw)
In-Reply-To: <20210117201014.271610-2-alxndr@bu.edu>
On 17/01/2021 21.10, Alexander Bulekov wrote:
> Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
> ---
> docs/devel/fuzzing.rst | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/docs/devel/fuzzing.rst b/docs/devel/fuzzing.rst
> index 8792358854..b9bb07988b 100644
> --- a/docs/devel/fuzzing.rst
> +++ b/docs/devel/fuzzing.rst
> @@ -119,7 +119,7 @@ Adding a new fuzzer
>
> Coverage over virtual devices can be improved by adding additional fuzzers.
> Fuzzers are kept in ``tests/qtest/fuzz/`` and should be added to
> -``tests/qtest/fuzz/Makefile.include``
> +``tests/qtest/fuzz/meson.build``
>
> Fuzzers can rely on both qtest and libqos to communicate with virtual devices.
>
> @@ -128,8 +128,7 @@ Fuzzers can rely on both qtest and libqos to communicate with virtual devices.
> 2. Write the fuzzing code using the libqtest/libqos API. See existing fuzzers
> for reference.
>
> -3. Register the fuzzer in ``tests/fuzz/Makefile.include`` by appending the
> - corresponding object to fuzz-obj-y
> +3. Add the fuzzer to ``tests/qtest/fuzz/meson.build``.
>
> Fuzzers can be more-or-less thought of as special qtest programs which can
> modify the qtest commands and/or qtest command arguments based on inputs
>
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2021-01-18 7:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 20:10 [PATCH 0/2] Small fuzzer-related changes Alexander Bulekov
2021-01-17 20:10 ` [PATCH 1/2] docs/fuzz: fix pre-meson path Alexander Bulekov
2021-01-18 7:50 ` Thomas Huth [this message]
2021-01-17 20:10 ` [PATCH 2/2] fuzz: log the arguments used to initialize QEMU Alexander Bulekov
2021-01-18 7:50 ` Thomas Huth
2021-01-18 8:43 ` pending fuzzing patches (was Re: [PATCH 2/2] fuzz: log the arguments used to initialize QEMU) Paolo Bonzini
2021-01-18 9:30 ` Thomas Huth
2021-01-18 13:38 ` Paolo Bonzini
2021-01-18 13:54 ` 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=d94da0a9-0b54-9b65-cc3e-4232e51f1cab@redhat.com \
--to=thuth@redhat.com \
--cc=alxndr@bu.edu \
--cc=bsd@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).