bonding: handle slave's name change with primary_slave logic
authorVeaceslav Falico <vfalico@redhat.com>
Thu, 16 Jan 2014 01:04:29 +0000 (02:04 +0100)
committerDavid S. Miller <davem@davemloft.net>
Fri, 17 Jan 2014 01:26:47 +0000 (17:26 -0800)
commit3ec775b9fb950db19175ab7984a0d65fda1142b4
treee0ed6d128eac94293e4b9171f55527d87969ce60
parent6c80563c2fdd9b32e37e2570e5b1ba9befd591c0
bonding: handle slave's name change with primary_slave logic

Currently, if a slave's name change, we just pass it by. However, if the
slave is a current primary_slave, then we end up with using a slave, whose
name != params.primary, for primary_slave. And vice-versa, if we don't have
a primary_slave but have params.primary set - we will not detected a new
primary_slave.

Fix this by catching the NETDEV_CHANGENAME event and setting primary_slave
accordingly. Also, if the primary_slave was changed, issue a reselection of
the active slave, cause the priorities have changed.

Reported-by: Ding Tianhong <dingtianhong@huawei.com>
CC: Ding Tianhong <dingtianhong@huawei.com>
CC: Jay Vosburgh <fubar@us.ibm.com>
CC: Andy Gospodarek <andy@greyhouse.net>
Signed-off-by: Veaceslav Falico <vfalico@redhat.com>
Acked-by: Ding Tianhong <dingtianhong@huawei.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
drivers/net/bonding/bond_main.c