From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org, chris@linuxinfotag.de
Subject: Re: [Qemu-devel] Solution for qemu mcast / ipv6?
Date: Tue, 10 Mar 2009 16:11:37 +0000 [thread overview]
Message-ID: <200903101611.38454.paul@codesourcery.com> (raw)
In-Reply-To: <20090310155033.GB8323@silmor.de>
Using diff -up makes patches much easier to review.
> @@ -303,6 +303,13 @@ qemu_format_nic_info_str
> vc->model,
> macaddr[0], macaddr[1], macaddr[2],
> macaddr[3], macaddr[4], macaddr[5]);
> + /* copy mac address into struct for quick matching */
> + vc->macaddress[0] = macaddr[0];
> + vc->macaddress[1] = macaddr[1];
> + vc->macaddress[2] = macaddr[2];
> + vc->macaddress[3] = macaddr[3];
> + vc->macaddress[4] = macaddr[4];
> + vc->macaddress[5] = macaddr[5];
> }
This is almost certainly the wrong place to do this.
> Now the question: Is this a proper solution?
No.
> Does it break anything?
Yes.
You can't make any assumptions about MAC addresses. The guest may choose to
use a different MAC address, or it may be acting as a hub/switch and
generating packets from many different MAC addresses.
The bug is in the the mcast socket code. You need to fix that to stop looping
back all the packets.
Paul
next prev parent reply other threads:[~2009-03-10 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 15:50 [Qemu-devel] Solution for qemu mcast / ipv6? Christian Perle
2009-03-10 16:11 ` Paul Brook [this message]
2009-03-10 20:30 ` Christian Perle
2009-03-10 23:16 ` Paul Brook
2009-03-10 23:55 ` Jamie Lokier
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=200903101611.38454.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=chris@linuxinfotag.de \
--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).