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, 1 Mar 2016 17:46:46 -0800 From: David Ahern <dsa@...ulusnetworks.com> To: David Miller <davem@...emloft.net> Cc: netdev@...r.kernel.org Subject: Re: [PATCH net-next] net: ipv6/l3mdev: Move host route on saved address if necessary On 3/1/16 2:23 PM, David Miller wrote: > From: David Ahern <dsa@...ulusnetworks.com> > Date: Sat, 27 Feb 2016 09:59:17 -0800 > >> Commit f1705ec197e70 allows IPv6 addresses to be retained on a link down. >> The address can have a cached host route which can point to the wrong >> FIB table if the L3 enslavement is changed (e.g., route can point to local >> table instead of VRF table if device is added to an L3 domain). >> >> On link up check the table of the cached host route against the FIB >> table associated with the device and correct if needed. >> >> Signed-off-by: David Ahern <dsa@...ulusnetworks.com> > > Ugly... but applied, thanks. > This is an example of what I meant by complications with the suggestion of stashing the prefix route. Would you prefer the host route always get freed on a down and re-created on an up?
Powered by blists - more mailing lists