From: Thomas Huth <thuth@redhat.com>
To: Lin Ma <lma@suse.com>, qemu-devel@nongnu.org
Cc: jasowang@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] net: Fix a potential segfault
Date: Mon, 11 Jun 2018 09:46:12 +0200 [thread overview]
Message-ID: <739f8a81-a519-9eb2-8b6e-8e7bf9e2ff81@redhat.com> (raw)
In-Reply-To: <20180611070609.9482-1-lma@suse.com>
On 11.06.2018 09:06, Lin Ma wrote:
> If user forgets to provide any backend types for '-netdev' in qemu CLI,
> It triggers seg fault.
>
> e.g.
>
> Expected:
> $ qemu -netdev id=net0
> qemu-system-x86_64: Parameter 'type' is missing
>
> Actual:
> $ qemu -netdev id=net0
> Segmentation fault (core dumped)
Ok, thanks for adding the description!
> Signed-off-by: Lin Ma <lma@suse.com>
> ---
> net/net.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/net/net.c b/net/net.c
> index efb9eaf779..f89790be4a 100644
> --- a/net/net.c
> +++ b/net/net.c
> @@ -1093,9 +1093,12 @@ static int net_client_init(QemuOpts *opts, bool is_netdev, Error **errp)
> int ret = -1;
> Visitor *v = opts_visitor_new(opts);
>
> - if (is_netdev && is_help_option(qemu_opt_get(opts, "type"))) {
> - show_netdevs();
> - exit(0);
> + if (is_netdev) {
> + const char *type = qemu_opt_get(opts, "type");
> + if (type && is_help_option(type)) {
> + show_netdevs();
> + exit(0);
> + }
> } else {
> /* Parse convenience option format ip6-net=fec0::0[/64] */
> const char *ip6_net = qemu_opt_get(opts, "ipv6-net");
>
I think you've got to do it in a slightly different way:
const char *type = qemu_opt_get(opts, "type");
if (is_netdev && type && is_help_option(type)) {
show_netdevs();
exit(0);
} else ...
otherwise the "else" branch is not entered anymore in case it is a
non-help netdev option.
Thomas
prev parent reply other threads:[~2018-06-11 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 7:06 [Qemu-devel] [PATCH v2] net: Fix a potential segfault Lin Ma
2018-06-11 7:46 ` Thomas Huth [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=739f8a81-a519-9eb2-8b6e-8e7bf9e2ff81@redhat.com \
--to=thuth@redhat.com \
--cc=jasowang@redhat.com \
--cc=lma@suse.com \
--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).