From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, afaerber@suse.de, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH 4/7] qdev-monitor: Fix check for full bus
Date: Mon, 08 Jun 2015 13:39:43 -0600 [thread overview]
Message-ID: <5575EF7F.4090300@redhat.com> (raw)
In-Reply-To: <1433789877-6950-5-git-send-email-armbru@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
On 06/08/2015 12:57 PM, Markus Armbruster wrote:
> Property bus has always been too screwed up to be really usable for
> values other than plain bus IDs. This just fixes a bug that crept in
> in commit 1395af6 "qdev: add a maximum device allowed field for the
> bus."
>
> It doesn't always fail when it should:
>
> $ qemu-system-x86_64 -nodefaults -device virtio-serial-pci -device virtio-rng-device,bus=pci.0/virtio-serial-pci/virtio-bus
>
> Happily plugs the virtio-rng-device into the virtio-bus provided by
> virtio-serial-pci, even though its only slot is already occupied by a
> virtio-serial-device.
>
> And sometimes fails when it shouldn't:
>
> $ qemu-system-x86_64 -nodefaults -device virtio-serial-pci -device virtserialport,bus=virtio-bus/virtio-serial-device
>
> Yes, the virtio-bus is full, but the virtio-serial-bus provided by
> virtio-serial-device isn't, and that's the one we're trying to use.
>
> Root cause: we check "bus full" when we resolve the first element of
> the path. That's the correct one only when it's also the last one.
>
> Fix by moving the "bus full" check to right before we return a bus.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> qdev-monitor.c | 31 +++++++++++++++++--------------
> 1 file changed, 17 insertions(+), 14 deletions(-)
>
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-06-08 19:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 18:57 [Qemu-devel] [PATCH 0/7] qdev: Mostly wean off QError Markus Armbruster
2015-06-08 18:57 ` [Qemu-devel] [PATCH 1/7] qdev: Deprecated qdev_init() is finally unused, drop Markus Armbruster
2015-06-08 19:03 ` Eric Blake
2015-06-08 18:57 ` [Qemu-devel] [PATCH 2/7] qdev: Un-deprecate qdev_init_nofail() Markus Armbruster
2015-06-08 19:12 ` Eric Blake
2015-06-08 18:57 ` [Qemu-devel] [PATCH 3/7] qdev-monitor: Stop error avalance in qbus_find_recursive() Markus Armbruster
2015-06-08 19:35 ` Eric Blake
2015-06-08 18:57 ` [Qemu-devel] [PATCH 4/7] qdev-monitor: Fix check for full bus Markus Armbruster
2015-06-08 19:39 ` Eric Blake [this message]
2015-06-08 18:57 ` [Qemu-devel] [PATCH 5/7] qdev-monitor: Convert qbus_find() to Error Markus Armbruster
2015-06-08 19:53 ` Eric Blake
2015-06-09 6:07 ` Markus Armbruster
2015-06-08 18:57 ` [Qemu-devel] [PATCH 6/7] qdev-monitor: Propagate errors through set_property() Markus Armbruster
2015-06-08 19:56 ` Eric Blake
2015-06-08 18:57 ` [Qemu-devel] [PATCH 7/7] qdev-monitor: Propagate errors through qdev_device_add() Markus Armbruster
2015-06-08 20:04 ` Eric Blake
2015-06-09 6:12 ` Markus Armbruster
2015-06-09 10:54 ` Eric Blake
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=5575EF7F.4090300@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.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).