Jay Vosburgh 40baec2257 bonding: fix panic on non-ARPHRD_ETHER enslave failure ... Since commit 7d5cd2ce529b, when bond_enslave fails on devices that are not ARPHRD_ETHER, if needed, it resets the bonding device back to ARPHRD_ETHER by calling ether_setup. Unfortunately, ether_setup clobbers dev->flags, clearing IFF_UP if the bond device is up, leaving it in a quasi-down state without having actually gone through dev_close. For bonding, if any periodic work queue items are active (miimon, arp_interval, etc), those will remain running, as they are stopped by bond_close. At this point, if the bonding module is unloaded or the bond is deleted, the system will panic when the work function is called. This panic is resolved by calling dev_close on the bond itself prior to calling ether_setup. Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com> Signed-off-by: Jay Vosburgh <jay.vosburgh@canonical.com> Fixes: 7d5cd2ce52 ("bonding: correctly handle bonding type change on enslave failure") Acked-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2015-11-07 13:17:32 -05:00
..
bond_3ad.c	bonding: simplify / unify event handling code for 3ad mode.	2015-11-02 22:52:24 -05:00
bond_alb.c
bond_debugfs.c
bond_main.c	bonding: fix panic on non-ARPHRD_ETHER enslave failure	2015-11-07 13:17:32 -05:00
bond_netlink.c	bonding: add tlb_dynamic_lb netlink support	2015-07-31 15:35:55 -07:00
bond_options.c	Changes for 4.3	2015-09-09 08:33:31 -07:00
bond_procfs.c
bond_sysfs_slave.c
bond_sysfs.c
bonding_priv.h
Makefile