correct behavior when modify primary via sysfs
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 11 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | bonding:record primary when modify it via sysfsdrivers/ | +6 | 5 replies | |
| 2/3 | bonding:check mode when modify primary_reselectdrivers/ | +7 | 4 replies | |
| 3/3 | bonding:force to use primary slavedrivers/ | +1 | 5 replies |
Reviews trailers per patch
1 of 3 patches has a Reviewed-by or Acked-by.
| Patch | Nicolas de Pesloüan |
|---|---|
| 1/3 | A-b |
| 2/3 | |
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH net 0/3] correct behavior when modify primary via sysfs
There is a problem that when we set primary slave with module parameters, bond will always use this primary slave as active slave.
But when we modify primary slave via sysfs, it will call bond_should_change_active() and take into account primary_reselect.
And I think we should use the new primary slave as the new active slave regardless of the value of primary_reselect.
Thus the behavior is the same with module parameters and meets the administrator's expectation.
Weiping Pan (3):
bonding:record primary when modify it via sysfs
bonding:check mode when modify primary_reselect
bonding:force to use primary slave
drivers/net/bonding/bond_sysfs.c | 16 ++++++++++++++-- 1 files changed, 14 insertions(+), 2 deletions(-)
Signature · 1 line
1.7.4