bonding: Fix some issues for fail_over_mac

Started by Ding Tianhong on Jan 21, 2014

DORMANTno replies SUPERSEDED

Status: Superseded by v3 (posted 2014-01-24). [go to v3]

Revision v1 (2 revisions archived).

Revisions (2)
  1. v1 current re-posted go to this post
  2. v3 [diff against previous] re-posted go to this post

open the first message on its own page

Message details and related content
The parameter fail_over_mac only affect active-backup mode, if it was
set to active or follow and works with other modes, just like RR or XOR
mode, the bonding could not set all slaves to the master's address, it
will cause the slave could not work well with master.

So set the fail_over_mac to none if the mode is not active-backup and
slight optimization for bond_set_mac_address().

Ding Tianhong (5):
  bonding: The fail_over_mac should be set only in ACTIVE_BACKUP mode
  bonding: don't set fail_over_mac if the mode is not active backup
  bonding: bonding: set fail_over_mac to none if new mode is not active-backup
  bonding: set fail_over_mac to active only in active-backup mode at
    enslavement
  bonding: remove the redundant judgements for bond_set_mac_address()

 drivers/net/bonding/bond_main.c    | 19 +++++++------------
 drivers/net/bonding/bond_options.c | 12 ++++++++++++
 2 files changed, 19 insertions(+), 12 deletions(-)

-- 
1.8.0
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help