From: Markus Armbruster <armbru@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Mark McLoughlin <markmc@redhat.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] qdev: Catch attempt to attach more than one device to a netdev
Date: Thu, 25 Feb 2010 15:32:17 +0100 [thread overview]
Message-ID: <m3eik9mln2.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <20100225120848.GA9223@redhat.com> (Michael S. Tsirkin's message of "Thu, 25 Feb 2010 14:08:48 +0200")
"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Thu, Feb 25, 2010 at 01:07:54PM +0100, Markus Armbruster wrote:
>> "Michael S. Tsirkin" <mst@redhat.com> writes:
>>
>> > On Thu, Feb 25, 2010 at 11:10:15AM +0100, Markus Armbruster wrote:
>> >> Guest device and host netdev are peers, i.e. it's a 1:1 relation.
>> >> However, we fail to enforce that:
>> >>
>> >> $ qemu -nodefaults --nographic -netdev user,id=net0 -device e1000,netdev=net0 -device virtio-net-pci,netdev=net0 -monitor stdio
>> >> QEMU 0.12.50 monitor - type 'help' for more information
>> >> (qemu) info network
>> >> Devices not on any VLAN:
>> >> net0: net=10.0.2.0, restricted=n peer=virtio-net-pci.0
>> >> e1000.0: model=e1000,macaddr=52:54:00:12:34:56 peer=net0
>> >> virtio-net-pci.0: model=virtio-net-pci,macaddr=52:54:00:12:34:57 peer=net0
>> >>
>> >> It's all downhill from there.
>> >>
>> >> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>> >> ---
>> >> hw/qdev-properties.c | 3 +++
>> >> net.c | 1 +
>> >> 2 files changed, 4 insertions(+), 0 deletions(-)
>> >>
>> >> diff --git a/hw/qdev-properties.c b/hw/qdev-properties.c
>> >> index 277ff9e..89efd91 100644
>> >> --- a/hw/qdev-properties.c
>> >> +++ b/hw/qdev-properties.c
>> >> @@ -341,6 +341,9 @@ static int parse_netdev(DeviceState *dev, Property *prop, const char *str)
>> >> *ptr = qemu_find_netdev(str);
>> >> if (*ptr == NULL)
>> >> return -1;
>> >> + if ((*ptr)->peer) {
>> >> + return -1;
>> >> + }
>> >
>> > Not even -EBUSY?
>> > Can this produce a helpful diagnostic message?
>>
>> Callers take care of that. It's how property parse methods work.
>> In this case:
>>
>> property "virtio-net-pci.netdev": failed to parse "net0"
>> can't set property "netdev" to "net0" for "virtio-net-pci"
>
> Yes, but does not tell you why. If parse_netdev even just returned a meaningful
> error code, we could see:
> can't set property "netdev" to "net0" for "virtio-net-pci":
> device or resource busy.
>
> which is at least a hint that something else uses it.
>
> As it is, it looks like qemu could not parse "net0"
> which is not really right.
Gerd, what do you think about changing the contract for property parse
methods to return -EINVAL, -EBUSY and such?
next prev parent reply other threads:[~2010-02-25 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 10:10 [Qemu-devel] [PATCH] qdev: Catch attempt to attach more than one device to a netdev Markus Armbruster
2010-02-25 11:42 ` [Qemu-devel] " Michael S. Tsirkin
2010-02-25 12:07 ` Markus Armbruster
2010-02-25 12:08 ` Michael S. Tsirkin
2010-02-25 12:49 ` Markus Armbruster
2010-02-25 14:32 ` Markus Armbruster [this message]
2010-02-25 14:38 ` Gerd Hoffmann
2010-02-26 9:30 ` Markus Armbruster
2010-02-26 10:05 ` Gerd Hoffmann
2010-02-26 14:41 ` Markus Armbruster
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=m3eik9mln2.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=markmc@redhat.com \
--cc=mst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.