netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: John Fastabend <john.r.fastabend@intel.com>
Cc: Vladislav Yasevich <vyasevic@redhat.com>,
	netdev@vger.kernel.org, Jason Wang <jasowang@redhat.com>,
	roopa@cumulusnetworks.com
Subject: Re: [PATCH] macvlan: Allow setting multicast filter on all macvlan types
Date: Sun, 17 Aug 2014 12:54:38 +0200	[thread overview]
Message-ID: <20140817105438.GE21622@redhat.com> (raw)
In-Reply-To: <53EE59BC.1070605@intel.com>

On Fri, Aug 15, 2014 at 12:04:28PM -0700, John Fastabend wrote:
> On 08/15/2014 10:04 AM, Vladislav Yasevich wrote:
> > Currently, macvlan code restricts multicast and unicast
> > filter setting only to passthru devices.  As a result,
> > if a guest using macvtap wants to receive multicast
> > traffic, it has to set IFF_ALLMULTI or IFF_PROMISC.
> > 
> > This patch makes it possible to use the fdb interface
> > to add multicast addresses to the filter thus allowing
> > a guest to receive only targeted multicast traffic.
> > 
> > CC: John Fastabend <john.r.fastabend@intel.com>
> > CC: Michael S. Tsirkin <mst@redhat.com>
> > CC: Jason Wang <jasowang@redhat.com>
> > Signed-off-by: Vladislav Yasevich <vyasevic@redhat.com>
> > ---
> 
> Acked-by: John Fastabend <john.r.fastabend@intel.com>
> 
> Looks good to me. Although I am trying to recall why
> we restrict unicast addresses? It looks like an additional
> check could be made to detect duplicate MAC addresses
> in fdb_add and then we could support this as well. But
> I might be missing why this wasn't supported originally.
> 
> Thanks,
> John

It's not just another macvlan: we need to avoid
conflicts with the underlying device itself.

Although I note that the relevant check when
creating macvlans in macvlan_addr_busy
isn't very robust either: if device address is later
reprogrammed, we can get a conflict.
But it seems better to fix that rather than propagate
the bug in more places.

We would also need to populate the mac hash.

So a bit more code would be needed.

-- 
MST

  parent reply	other threads:[~2014-08-17 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 17:04 [PATCH] macvlan: Allow setting multicast filter on all macvlan types Vladislav Yasevich
2014-08-15 19:04 ` John Fastabend
2014-08-15 19:54   ` Vlad Yasevich
2014-08-17 10:54   ` Michael S. Tsirkin [this message]
2014-08-17  9:43 ` Michael S. Tsirkin
2014-08-21 23:54 ` David Miller

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=20140817105438.GE21622@redhat.com \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=john.r.fastabend@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=vyasevic@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).