netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Rundong Ge <rdong.ge@gmail.com>, andrew@lunn.ch
Cc: vivien.didelot@gmail.com, davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] net: dsa: slave: Don't propagate flag changes on down slave interfaces
Date: Sat, 2 Feb 2019 09:05:11 -0800	[thread overview]
Message-ID: <7f8fadc6-1bb5-03b5-4f5e-a407e9116399@gmail.com> (raw)
In-Reply-To: <20190202142935.3090-1-rdong.ge@gmail.com>

Le 2/2/19 à 6:29 AM, Rundong Ge a écrit :
> The unbalance of master's promiscuity or allmulti will happen after ifdown
> and ifup a slave interface which is in a bridge.
> 
> When we ifdown a slave interface , both the 'dsa_slave_close' and
> 'dsa_slave_change_rx_flags' will clear the master's flags. The flags
> of master will be decrease twice.
> In the other hand, if we ifup the slave interface again, since the
> slave's flags were cleared the 'dsa_slave_open' won't set the master's
> flag, only 'dsa_slave_change_rx_flags' that triggered by 'br_add_if'
> will set the master's flags. The flags of master is increase once.
> 
> Only propagating flag changes when a slave interface is up makes
> sure this does not happen. The 'vlan_dev_change_rx_flags' had the
> same problem and was fixed, and changes here follows that fix.

VLAN code under net/8021q/vlan_dev.c::vlan_dev_change_rx_flags() appears
to do the same thing that you are proposing, so this looks fine to me.
Since that is a bugfix, we should probably add:

Fixes: 91da11f870f0 ("net: Distributed Switch Architecture protocol
support")

?

> 
> Signed-off-by: Rundong Ge <rdong.ge@gmail.com>
> ---
>  net/dsa/slave.c | 13 ++++++++-----
>  1 file changed, 8 insertions(+), 5 deletions(-)
> 
> diff --git a/net/dsa/slave.c b/net/dsa/slave.c
> index a3fcc1d..b5e4482 100644
> --- a/net/dsa/slave.c
> +++ b/net/dsa/slave.c
> @@ -140,11 +140,14 @@ static int dsa_slave_close(struct net_device *dev)
>  static void dsa_slave_change_rx_flags(struct net_device *dev, int change)
>  {
>  	struct net_device *master = dsa_slave_to_master(dev);
> -
> -	if (change & IFF_ALLMULTI)
> -		dev_set_allmulti(master, dev->flags & IFF_ALLMULTI ? 1 : -1);
> -	if (change & IFF_PROMISC)
> -		dev_set_promiscuity(master, dev->flags & IFF_PROMISC ? 1 : -1);
> +	if (dev->flags & IFF_UP) {
> +		if (change & IFF_ALLMULTI)
> +			dev_set_allmulti(master,
> +					 dev->flags & IFF_ALLMULTI ? 1 : -1);
> +		if (change & IFF_PROMISC)
> +			dev_set_promiscuity(master,
> +					    dev->flags & IFF_PROMISC ? 1 : -1);
> +	}
>  }
>  
>  static void dsa_slave_set_rx_mode(struct net_device *dev)
> 


-- 
Florian

  reply	other threads:[~2019-02-02 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-02 14:29 [PATCH] net: dsa: slave: Don't propagate flag changes on down slave interfaces Rundong Ge
2019-02-02 17:05 ` Florian Fainelli [this message]
2019-02-02 17:16   ` Andrew Lunn
2019-02-03  5:34     ` 戈润栋
2019-02-05  2:29   ` 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=7f8fadc6-1bb5-03b5-4f5e-a407e9116399@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=rdong.ge@gmail.com \
    --cc=vivien.didelot@gmail.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).