From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: "Cornelia Huck" <cohuck@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>
Subject: Re: [PATCH] qom/object: Display more helpful message when an interface is missing
Date: Sat, 18 Jan 2020 22:26:13 +0100 [thread overview]
Message-ID: <ccbaca59-eb9c-996c-7708-7c8438bda79f@redhat.com> (raw)
In-Reply-To: <20200118162348.17823-1-philmd@redhat.com>
On 18/01/20 17:23, Philippe Mathieu-Daudé wrote:
> When adding new devices implementing QOM interfaces, we might
> forgot to add the Kconfig dependency that pulls the required
> objects in when building.
>
> Since QOM dependencies are resolved at runtime, we don't get any
> link-time failures, and QEMU aborts while starting:
>
> $ qemu ...
> Segmentation fault (core dumped)
>
> (gdb) bt
> #0 0x00007ff6e96b1e35 in raise () from /lib64/libc.so.6
> #1 0x00007ff6e969c895 in abort () from /lib64/libc.so.6
> #2 0x00005572bc5051cf in type_initialize (ti=0x5572be6f1200) at qom/object.c:323
> #3 0x00005572bc505074 in type_initialize (ti=0x5572be6f1800) at qom/object.c:301
> #4 0x00005572bc505074 in type_initialize (ti=0x5572be6e48e0) at qom/object.c:301
> #5 0x00005572bc506939 in object_class_by_name (typename=0x5572bc56109a) at qom/object.c:959
> #6 0x00005572bc503dd5 in cpu_class_by_name (typename=0x5572bc56109a, cpu_model=0x5572be6d9930) at hw/core/cpu.c:286
>
> Since the caller has access to the qdev parent/interface names,
> we can simply display them to avoid starting a debugger:
>
> $ qemu ...
> qemu: missing interface 'fancy-if' for object 'fancy-dev'
> Aborted (core dumped)
>
> This commit is similar to e02bdf1cecd2 ("Display more helpful message
> when an object type is missing").
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> Cc: Cornelia Huck <cohuck@redhat.com>
> Cc: Stefano Garzarella <sgarzare@redhat.com>
> Cc: Daniel P. Berrangé <berrange@redhat.com>
> ---
> qom/object.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/qom/object.c b/qom/object.c
> index 0d971ca897..36123fb330 100644
> --- a/qom/object.c
> +++ b/qom/object.c
> @@ -317,6 +317,11 @@ static void type_initialize(TypeImpl *ti)
>
> for (i = 0; i < ti->num_interfaces; i++) {
> TypeImpl *t = type_get_by_name(ti->interfaces[i].typename);
> + if (!t) {
> + error_report("missing interface '%s' for object '%s'",
> + ti->interfaces[i].typename, parent->name);
> + abort();
> + }
> for (e = ti->class->interfaces; e; e = e->next) {
> TypeImpl *target_type = OBJECT_CLASS(e->data)->type;
>
>
Queued, thanks.
Paolo
next prev parent reply other threads:[~2020-01-18 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 16:23 [PATCH] qom/object: Display more helpful message when an interface is missing Philippe Mathieu-Daudé
2020-01-18 21:26 ` Paolo Bonzini [this message]
2020-01-20 8:58 ` Cornelia Huck
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=ccbaca59-eb9c-996c-7708-7c8438bda79f@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=ehabkost@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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).