From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Navid Emamdoost <navidem@google.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
zsm@google.com, Alexander Bulekov <alxndr@bu.edu>,
Paolo Bonzini <pbonzini@redhat.com>, Bandan Das <bsd@redhat.com>,
Fabiano Rosas <farosas@suse.de>,
Darren Kenny <darren.kenny@oracle.com>,
Qiuhao Li <Qiuhao.Li@outlook.com>,
Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH] tests/qtest/fuzz: Add generic fuzzer for VNC
Date: Fri, 10 Oct 2025 09:56:10 +0100 [thread overview]
Message-ID: <aOjKKgGEL5sYmhmD@redhat.com> (raw)
In-Reply-To: <20251009211114.2214848-1-navidem@google.com>
On Thu, Oct 09, 2025 at 09:11:14PM +0000, Navid Emamdoost wrote:
> Add a new generic fuzz target for the QEMU VNC server. This allows the
> generic fuzzer to directly exercise the VNC protocol implementation by
> connecting to a VNC unix socket.
>
> ---
>
> This new target increases code coverage in the VNC subsystem
> and related networking and I/O code.
> The baseline coverage below was generated by running all existing fuzz
> targets with the oss-fuzz corpus. The new target shows significant gains:
>
> ----------------------------------------------------------------------------
> File New Target Baseline Change
> ----------------------------------------------------------------------------
> vnc.c 339/3212 (10.6%) 3/3212 (0.1%) +336
> keymaps.c 91/184 (49.5%) 0/184 (0.0%) +91
> net-listener.c 76/198 (38.4%) 3/198 (1.5%) +73
> channel-socket.c 73/575 (12.7%) 19/575 (3.3%) +54
> qemu-sockets.c 44/1019 (4.3%) 0/1019 (0.0%) +44
> dns-resolver.c 28/145 (19.3%) 3/145 (2.1%) +25
> vnc-jobs.c 41/219 (18.7%) 0/219 (0.0%) +41
>
> Signed-off-by: Navid Emamdoost <navidem@google.com>
> ---
> tests/qtest/fuzz/generic_fuzz_configs.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/tests/qtest/fuzz/generic_fuzz_configs.h b/tests/qtest/fuzz/generic_fuzz_configs.h
> index ef0ad95712..2e802ab226 100644
> --- a/tests/qtest/fuzz/generic_fuzz_configs.h
> +++ b/tests/qtest/fuzz/generic_fuzz_configs.h
> @@ -247,6 +247,10 @@ const generic_fuzz_config predefined_configs[] = {
> .args = "-machine q35 -nodefaults "
> "-parallel file:/dev/null",
> .objects = "parallel*",
> + },{
> + .name = "vnc",
> + .args = "-machine q35 -nodefaults -vnc vnc=unix:/tmp/qemu-vnc.sock",
How about also adding ",websocket=unix:/tmp/qemu-vnc-ws.sock" ?
I'm guessing the fuzz tool is not intelligent enough to be able
to negotiate TLS over the connections ?
> + .objects = "*",
> }
> };
>
> --
> 2.51.0.740.g6adb054d12-goog
>
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-10-10 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 21:11 [PATCH] tests/qtest/fuzz: Add generic fuzzer for VNC Navid Emamdoost
2025-10-10 8:56 ` Daniel P. Berrangé [this message]
2025-10-10 15:15 ` Alexander Bulekov
2025-10-14 0:30 ` [PATCH v2 0/1] " Navid Emamdoost
2025-10-14 0:30 ` [PATCH v2 1/1] " Navid Emamdoost
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=aOjKKgGEL5sYmhmD@redhat.com \
--to=berrange@redhat.com \
--cc=Qiuhao.Li@outlook.com \
--cc=alxndr@bu.edu \
--cc=bsd@redhat.com \
--cc=darren.kenny@oracle.com \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=navidem@google.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=zsm@google.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).