netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: pch@ordbogen.com
Cc: kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [PATCH] macvlan: Don't propagate IFF_ALLMULTI changes on down interfaces.
Date: Mon, 12 May 2014 14:15:54 -0400 (EDT)	[thread overview]
Message-ID: <20140512.141554.1557022486435680828.davem@davemloft.net> (raw)
In-Reply-To: <20140512095953.076bd76d@pch.odense.ordbogen.com>

From: Peter Christensen <pch@ordbogen.com>
Date: Mon, 12 May 2014 09:59:53 +0200

> On Fri, 09 May 2014 16:02:25 -0400 (EDT)
> David Miller <davem@davemloft.net> wrote:
> 
>> From: Peter Christensen <pch@ordbogen.com>
>> Date: Thu,  8 May 2014 11:15:37 +0200
>> 
>> > Clearing the IFF_ALLMULTI flag on a down interface could cause an
>> > allmulti overflow on the underlying interface.
>> > 
>> > Attempting the set IFF_ALLMULTI on the underlying interface would
>> > cause an error and the log message:
>> > 
>> > "allmulti touches root, set allmulti failed."
>> > 
>> > Signed-off-by: Peter Christensen <pch@ordbogen.com>
>> 
>> Hmmm, but won't we lose this event once the interface is brought
>> back up?
> 
> No, macvlan_open and macvlan_stop already takes care of that (which is
> part of the reason the allmulti counter overflowed). Either
> macvlan_open and macvlan_close shouldn't touch the flag on the
> underlying interface, or
> macvlan_change_rx_flags shouldn't touch the underlying interface if the
> MACVLAN interface is down.
> 
> I though that it was probably better to make MACVLAN as non-intrusive
> to the underlying interface when the MACVLAN interface is down, so I
> opted for this solution.
> 
> Apparently the 802.1Q VLAN driver behaves
> exactly like that, and back in 2011 it got a patch similar to this one
> (commit deede2fabe24e00bd7e246eb81cd5767dc6fcfc7).

Thanks for the detailed explanation, applied and queued up for -stable, thanks!

      reply	other threads:[~2014-05-12 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08  9:15 [PATCH] macvlan: Don't propagate IFF_ALLMULTI changes on down interfaces Peter Christensen
2014-05-09 20:02 ` David Miller
2014-05-12  7:59   ` Peter Christensen
2014-05-12 18:15     ` David Miller [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=20140512.141554.1557022486435680828.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=pch@ordbogen.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).