| 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
| ||
|
Message-Id: <20151208.224032.2201079065584601145.davem@davemloft.net> Date: Tue, 08 Dec 2015 22:40:32 -0500 (EST) From: David Miller <davem@...emloft.net> To: dsa@...ulusnetworks.com Cc: netdev@...r.kernel.org, shm@...ulusnetworks.com Subject: Re: [PATCH net-next v2] net: Add fib rules at vrf device create From: David Ahern <dsa@...ulusnetworks.com> Date: Tue, 8 Dec 2015 20:08:31 -0700 > On 12/8/15 7:44 PM, David Miller wrote: >> Unfortunately it's too late for this, you should have considered this >> issue fully when VRF first went into an upstream release. >> >> If I add your change, the user experience is _worse_. >> >> Users on older kernels have to use the full sequence, then if they >> upgrade their kernels to one with this patch then the 'ru add' et >> al. commands will fail. >> > > Perhaps this is another fug (feature bug), they do not fail: > > root@...ny-jessie2:~# ip ru ls > 0: from all lookup local > 32760: from all iif vrf-green lookup vrf-green > 32761: from all oif vrf-green lookup vrf-green > 32762: from all iif vrf-blue lookup vrf-blue > 32763: from all oif vrf-blue lookup vrf-blue > 32764: from all iif vrf-red lookup vrf-red > 32765: from all oif vrf-red lookup vrf-red > 32766: from all lookup main > 32767: from all lookup default > > root@...ny-jessie2:~# ip ru add oif vrf-red lookup vrf-red Grrr... -- 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