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: Tue, 26 Apr 2011 22:09:06 -0400 From: Brian Haley <brian.haley@...com> To: Ben Hutchings <bhutchings@...arflare.com> CC: Jay Vosburgh <fubar@...ibm.com>, Andy Gospodarek <andy@...yhouse.net>, David Miller <davem@...emloft.net>, Patrick McHardy <kaber@...sh.net>, netdev@...r.kernel.org Subject: Re: [PATCH net-next-2.6] ipv4,ipv6,bonding: Restore control over number of peer notifications On 04/26/2011 09:25 PM, Ben Hutchings wrote: > For backward compatibility, we should retain the module parameters and > sysfs attributes to control the number of peer notifications > (gratuitous ARPs and unsolicited NAs) sent after bonding failover. > Also, it is possible for failover to take place even though the new > active slave does not have link up, and in that case the peer > notification should be deferred until it does. > > Change ipv4 and ipv6 so they do not automatically send peer > notifications on bonding failover. > > Change the bonding driver to send separate NETDEV_NOTIFY_PEERS > notifications when the link is up, as many times as requested. Since > it does not directly control which protocols send notifications, make > num_grat_arp and num_unsol_na aliases for a single parameter. Bump > the bonding version number and update its documentation. > > Signed-off-by: Ben Hutchings <bhutchings@...arflare.com> Signed-off-by: Brian Haley <brian.haley@...com> -- 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