summaryrefslogtreecommitdiffstats
path: root/net/wimax
diff options
context:
space:
mode:
authorMahesh Bandewar <maheshb@google.com>2016-09-01 22:18:34 -0700
committerDavid S. Miller <davem@davemloft.net>2016-09-04 11:41:12 -0700
commit24b27fc4cdf9e10c5e79e5923b6b7c2c5c95096c (patch)
treefc45153ddf713cf24fe6916d531b91c9cee34d91 /net/wimax
parent312565a0c38ab12275b6ca5ec75d21f3f3ace844 (diff)
downloadlinux-24b27fc4cdf9e10c5e79e5923b6b7c2c5c95096c.tar.gz
linux-24b27fc4cdf9e10c5e79e5923b6b7c2c5c95096c.tar.bz2
linux-24b27fc4cdf9e10c5e79e5923b6b7c2c5c95096c.zip
bonding: Fix bonding crash
Following few steps will crash kernel - (a) Create bonding master > modprobe bonding miimon=50 (b) Create macvlan bridge on eth2 > ip link add link eth2 dev mvl0 address aa:0:0:0:0:01 \ type macvlan (c) Now try adding eth2 into the bond > echo +eth2 > /sys/class/net/bond0/bonding/slaves <crash> Bonding does lots of things before checking if the device enslaved is busy or not. In this case when the notifier call-chain sends notifications, the bond_netdev_event() assumes that the rx_handler /rx_handler_data is registered while the bond_enslave() hasn't progressed far enough to register rx_handler for the new slave. This patch adds a rx_handler check that can be performed right at the beginning of the enslave code to avoid getting into this situation. Signed-off-by: Mahesh Bandewar <maheshb@google.com> Acked-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/wimax')
0 files changed, 0 insertions, 0 deletions