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: Thu, 10 Nov 2016 18:14:39 +0900 From: Lorenzo Colitti <lorenzo@...gle.com> To: David Lebrun <david.lebrun@...ouvain.be> Cc: David Miller <davem@...emloft.net>, "netdev@...r.kernel.org" <netdev@...r.kernel.org> Subject: Re: [PATCH net-next v5 0/9] net: add support for IPv6 Segment Routing On Thu, Nov 10, 2016 at 6:09 PM, David Lebrun <david.lebrun@...ouvain.be> wrote: > Oops. The easiest fix I can think of is adding an option to > enable/disable seg6's LWT which would select CONFIG_LWTUNNEL. That would > still let the core SR processing be enabled by default. So you'd split SRH functionality in three parts? Core (default on), lwtunnel (default off) and inline? It seems to me that once you've done the work to enable the core code to work when CONFIG_LWTUNNEL is off, you can just enable/disable the LWT part of SRH depending on whether CONFIG_LWTUNNEL is compiled in or not. That might save you a config option.
Powered by blists - more mailing lists