From: Marcel Apfelbaum <marcel.a@redhat.com>
To: armbru@redhat.com
Cc: kwolf@redhat.com, peter.maydell@linaro.org,
qemu-devel@nongnu.org, borntraeger@de.ibm.com,
aliguori@amazon.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v3 10/10] qdev: Do not let the user try to device_add when it cannot work
Date: Thu, 31 Oct 2013 14:41:19 +0200 [thread overview]
Message-ID: <1383223279.4734.40.camel@localhost.localdomain> (raw)
In-Reply-To: <1383150524-16250-11-git-send-email-armbru@redhat.com>
On Wed, 2013-10-30 at 17:28 +0100, armbru@redhat.com wrote:
> From: Markus Armbruster <armbru@redhat.com>
>
> Such devices have always been unavailable and omitted from the list of
> available devices shown by device_add help. Until commit 18b6dad
> silently broke the former, setting up nasty traps for unwary users,
> like this one:
>
> $ qemu-system-x86_64 -nodefaults -monitor stdio -display none
> QEMU 1.6.50 monitor - type 'help' for more information
> (qemu) device_add apic
> Segmentation fault (core dumped)
>
> I call that a regression. Fix it.
Seems OK to me.
Reviewed-by: Marcel Apfelbaum <marcel.a@redhat.com>
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> qdev-monitor.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/qdev-monitor.c b/qdev-monitor.c
> index 36f6f09..d3d87a3 100644
> --- a/qdev-monitor.c
> +++ b/qdev-monitor.c
> @@ -477,13 +477,13 @@ DeviceState *qdev_device_add(QemuOpts *opts)
> }
> }
>
> - if (!obj) {
> + k = DEVICE_CLASS(obj);
> +
> + if (!k || k->cannot_instantiate_with_device_add_yet) {
> qerror_report(QERR_INVALID_PARAMETER_VALUE, "driver", "device type");
> return NULL;
> }
>
> - k = DEVICE_CLASS(obj);
> -
> /* find bus */
> path = qemu_opt_get(opts, "bus");
> if (path != NULL) {
prev parent reply other threads:[~2013-10-31 12:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 16:28 [Qemu-devel] [PATCH v3 00/10] Clean up and fix no_user armbru
2013-10-30 16:28 ` [Qemu-devel] [PATCH v3 01/10] qdev: Replace no_user by cannot_instantiate_with_device_add_yet armbru
2013-10-30 16:28 ` [Qemu-devel] [PATCH v3 02/10] sysbus: Set cannot_instantiate_with_device_add_yet armbru
2013-10-30 16:28 ` [Qemu-devel] [PATCH v3 03/10] cpu: Document why cannot_instantiate_with_device_add_yet armbru
2013-10-30 16:28 ` [Qemu-devel] [PATCH v3 04/10] apic: " armbru
2013-10-30 16:28 ` [Qemu-devel] [PATCH v3 05/10] pci-host: Consistently set cannot_instantiate_with_device_add_yet armbru
2013-10-30 16:28 ` [Qemu-devel] [PATCH v3 06/10] ich9: Document why cannot_instantiate_with_device_add_yet armbru
2013-10-30 16:28 ` [Qemu-devel] [PATCH v3 07/10] piix3 piix4: Clean up use of cannot_instantiate_with_device_add_yet armbru
2013-10-31 9:00 ` Marcel Apfelbaum
2013-10-31 10:29 ` Markus Armbruster
2013-10-31 13:12 ` Marcel Apfelbaum
2013-10-30 16:28 ` [Qemu-devel] [PATCH v3 08/10] vt82c686: " armbru
2013-10-30 16:28 ` [Qemu-devel] [PATCH v3 09/10] isa: " armbru
2013-10-31 12:44 ` Marcel Apfelbaum
2013-10-30 16:28 ` [Qemu-devel] [PATCH v3 10/10] qdev: Do not let the user try to device_add when it cannot work armbru
2013-10-31 12:41 ` Marcel Apfelbaum [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=1383223279.4734.40.camel@localhost.localdomain \
--to=marcel.a@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--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).