qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Alexander Bulekov <alxndr@bu.edu>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, Bandan Das <bsd@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH 2/2] fuzz: log the arguments used to initialize QEMU
Date: Mon, 18 Jan 2021 08:50:39 +0100	[thread overview]
Message-ID: <d97f0ac0-244b-eecf-848e-c09c1fcea474@redhat.com> (raw)
In-Reply-To: <20210117201014.271610-3-alxndr@bu.edu>

On 17/01/2021 21.10, Alexander Bulekov wrote:
> This is useful for building reproducers. Instead checking the code or
> the QEMU_FUZZ_ARGS, the arguments are at the top of the crash log.
> 
> Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
> ---
>   tests/qtest/fuzz/fuzz.c | 11 ++++++++++-
>   1 file changed, 10 insertions(+), 1 deletion(-)
> 
> diff --git a/tests/qtest/fuzz/fuzz.c b/tests/qtest/fuzz/fuzz.c
> index 238866a037..496d11a231 100644
> --- a/tests/qtest/fuzz/fuzz.c
> +++ b/tests/qtest/fuzz/fuzz.c
> @@ -159,6 +159,8 @@ int LLVMFuzzerInitialize(int *argc, char ***argv, char ***envp)
>       char *target_name;
>       const char *bindir;
>       char *datadir;
> +    GString *cmd_line;
> +    gchar *pretty_cmd_line;
>       bool serialize = false;
>   
>       /* Initialize qgraph and modules */
> @@ -217,7 +219,7 @@ int LLVMFuzzerInitialize(int *argc, char ***argv, char ***envp)
>       }
>   
>       /* Run QEMU's softmmu main with the fuzz-target dependent arguments */
> -    GString *cmd_line = fuzz_target->get_init_cmdline(fuzz_target);
> +    cmd_line = fuzz_target->get_init_cmdline(fuzz_target);
>       g_string_append_printf(cmd_line, " %s -qtest /dev/null ",
>                              getenv("QTEST_LOG") ? "" : "-qtest-log none");
>   
> @@ -226,6 +228,13 @@ int LLVMFuzzerInitialize(int *argc, char ***argv, char ***envp)
>       wordexp(cmd_line->str, &result, 0);
>       g_string_free(cmd_line, true);
>   
> +    if (getenv("QTEST_LOG")) {
> +        pretty_cmd_line  = g_strjoinv(" ", result.we_wordv + 1);
> +        printf("Starting %s with Arguments: %s\n",
> +                result.we_wordv[0], pretty_cmd_line);
> +        g_free(pretty_cmd_line);
> +    }
> +
>       qemu_init(result.we_wordc, result.we_wordv, NULL);
>   
>       /* re-enable the rcu atfork, which was previously disabled in qemu_init */
> 

Reviewed-by: Thomas Huth <thuth@redhat.com>



  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
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 [this message]
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=d97f0ac0-244b-eecf-848e-c09c1fcea474@redhat.com \
    --to=thuth@redhat.com \
    --cc=alxndr@bu.edu \
    --cc=bsd@redhat.com \
    --cc=lvivier@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).