lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 11 Jun 2012 17:00:19 +0800 From: Weiping Pan <wpan@...hat.com> To: netdev@...r.kernel.org Subject: [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(-) -- 1.7.4 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists