diff options
author | WANG Cong <xiyou.wangcong@gmail.com> | 2017-07-06 15:01:57 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-07-08 11:23:29 +0100 |
commit | f51048c3e07b68c90b21a77541fc4b208f9244d7 (patch) | |
tree | c8f485825b7b9ac43cdde73c4d174474b1498794 /Documentation | |
parent | 5dc314f8ded18e2b0ffce55a5f253c8aa759d51a (diff) | |
download | linux-stable-f51048c3e07b68c90b21a77541fc4b208f9244d7.tar.gz linux-stable-f51048c3e07b68c90b21a77541fc4b208f9244d7.tar.bz2 linux-stable-f51048c3e07b68c90b21a77541fc4b208f9244d7.zip |
bonding: avoid NETDEV_CHANGEMTU event when unregistering slave
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@6wind.com>
Reported-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: Jay Vosburgh <j.vosburgh@gmail.com>
Cc: Veaceslav Falico <vfalico@gmail.com>
Cc: Andy Gospodarek <andy@greyhouse.net>
Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions