[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170708.112418.240898091794587743.davem@davemloft.net>
Date: Sat, 08 Jul 2017 11:24:18 +0100 (WEST)
From: David Miller <davem@...emloft.net>
To: xiyou.wangcong@...il.com
Cc: netdev@...r.kernel.org, hongjun.li@...nd.com,
nicolas.dichtel@...nd.com, j.vosburgh@...il.com, vfalico@...il.com,
andy@...yhouse.net
Subject: Re: [Patch net] bonding: avoid NETDEV_CHANGEMTU event when
unregistering slave
From: Cong Wang <xiyou.wangcong@...il.com>
Date: Thu, 6 Jul 2017 15:01:57 -0700
> As Hongjun/Nicolas summarized in their original patch:
>
> "
> When a device changes from one netns to another, it's first unregistered,
> then the netns reference is updated and the dev is registered in the new
> netns. Thus, when a slave moves to another netns, it is first
> unregistered. This triggers a NETDEV_UNREGISTER event which is caught by
> the bonding driver. The driver calls bond_release(), which calls
> dev_set_mtu() and thus triggers NETDEV_CHANGEMTU (the device is still in
> the old netns).
> "
>
> This is a very special case, because the device is being unregistered
> no one should still care about the NETDEV_CHANGEMTU event triggered
> at this point, we can avoid broadcasting this event on this path,
> and avoid touching inetdev_event()/addrconf_notify() path.
>
> It requires to export __dev_set_mtu() to bonding driver.
>
> Reported-by: Hongjun Li <hongjun.li@...nd.com>
> Reported-by: Nicolas Dichtel <nicolas.dichtel@...nd.com>
> Cc: Jay Vosburgh <j.vosburgh@...il.com>
> Cc: Veaceslav Falico <vfalico@...il.com>
> Cc: Andy Gospodarek <andy@...yhouse.net>
> Signed-off-by: Cong Wang <xiyou.wangcong@...il.com>
Applied, thanks.
Powered by blists - more mailing lists