bonding: Fix some issues for fail_over_mac
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | bonding: The fail_over_mac should be set only in ACTIVE_BACKUP modedrivers/ | +5 | 2 replies | |
| 2/5 | bonding: don't set fail_over_mac if the mode is not active backupdrivers/ | +6 | 0 replies | |
| 3/5 | bonding: set fail_over_mac to none if new mode is not active-backupdrivers/ | +6 | 0 replies | |
| 4/5 | bonding: set fail_over_mac to active only in active-backup mode at enslavementdrivers/ | +2 | 0 replies | |
| 5/5 | bonding: remove the redundant judgements for bond_set_mac_address()drivers/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH net-next 0/5] bonding: Fix some issues for fail_over_mac
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(-)
Signature · 1 line
1.8.0