bonding: properly unset current_arp_slave on slave link up
authorVeaceslav Falico <vfalico@redhat.com>
Thu, 5 Apr 2012 03:47:43 +0000 (03:47 +0000)
committerBen Hutchings <ben@decadent.org.uk>
Fri, 11 May 2012 12:14:19 +0000 (13:14 +0100)
commit873f40f17a6a7063af86befe4ffe4f70d98a1b1b
treebfc7d03a8b23241d3cc39cf0b6ebaeb3f6899398
parent1bf5e1db2f65033fb7b80f63fabbe2b8bf2f0936
bonding: properly unset current_arp_slave on slave link up

[ Upstream commit 5a4309746cd74734daa964acb02690c22b3c8911 ]

When a slave comes up, we're unsetting the current_arp_slave without
removing active flags from it, which can lead to situations where we have
more than one slave with active flags in active-backup mode.

To avoid this situation we must remove the active flags from a slave before
removing it as a current_arp_slave.

Signed-off-by: Veaceslav Falico <vfalico@redhat.com>
Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
Signed-off-by: Andy Gospodarek <andy@greyhouse.net>
Signed-off-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
drivers/net/bonding/bond_main.c