From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: ehabkost@redhat.com, armbru@redhat.com,
Eric Blake <eblake@redhat.com>,
mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] hostmem: fix crash when querying empty host-nodes property via QMP
Date: Wed, 13 Feb 2019 13:44:28 +0100 [thread overview]
Message-ID: <20190213134428.11b03224@redhat.com> (raw)
In-Reply-To: <1549377087-205549-1-git-send-email-imammedo@redhat.com>
On Tue, 5 Feb 2019 15:31:27 +0100
Igor Mammedov <imammedo@redhat.com> wrote:
> QEMU will crashes with
> qapi/qobject-output-visitor.c:210: qobject_output_complete: Assertion `qov->root && ((&qov->stack)->slh_first == ((void *)0))' failed
> when trying to get value of empty hostmem.host-nodes property.
>
> Fix it by calling visitor even if host-nodes wasn't set
> before exiting from property getter to return empty list.
>
> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> ---
> backends/hostmem.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/backends/hostmem.c b/backends/hostmem.c
> index 0c8ef17..fe14be5 100644
> --- a/backends/hostmem.c
> +++ b/backends/hostmem.c
> @@ -86,7 +86,7 @@ host_memory_backend_get_host_nodes(Object *obj, Visitor *v, const char *name,
>
> value = find_first_bit(backend->host_nodes, MAX_NODES);
> if (value == MAX_NODES) {
> - return;
> + goto ret;
> }
>
> *node = g_malloc0(sizeof(**node));
> @@ -104,6 +104,7 @@ host_memory_backend_get_host_nodes(Object *obj, Visitor *v, const char *name,
> node = &(*node)->next;
> } while (true);
>
> +ret:
> visit_type_uint16List(v, name, &host_nodes, errp);
> }
>
Markus/Michael,
does this patch make sense from QAPI point of view?
next prev parent reply other threads:[~2019-02-13 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 14:31 [Qemu-devel] [PATCH] hostmem: fix crash when querying empty host-nodes property via QMP Igor Mammedov
2019-02-13 12:44 ` Igor Mammedov [this message]
2019-02-13 13:30 ` Markus Armbruster
2019-02-14 10:56 ` Igor Mammedov
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=20190213134428.11b03224@redhat.com \
--to=imammedo@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mdroth@linux.vnet.ibm.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).