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: Wed, 27 Mar 2019 09:46:52 +0000 From: Ido Schimmel <idosch@...lanox.com> To: David Ahern <dsahern@...nel.org> CC: "davem@...emloft.net" <davem@...emloft.net>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Jiri Pirko <jiri@...lanox.com>, Saeed Mahameed <saeedm@...lanox.com>, David Ahern <dsahern@...il.com> Subject: Re: [PATCH net-next 13/13] net: Use common nexthop init and release helpers On Tue, Mar 26, 2019 at 08:29:42PM -0700, David Ahern wrote: > From: David Ahern <dsahern@...il.com> > > With fib_nh_common in place, move common initialization and release > code into helpers used by both ipv4 and ipv6. For the moment, the init > is just the lwt encap and the release is both the net dev reference and s/net dev/netdev/ > the the lwt state reference. More will be added later. > > Signed-off-by: David Ahern <dsahern@...il.com> > --- > include/net/ip_fib.h | 4 ++++ > net/ipv4/fib_semantics.c | 60 +++++++++++++++++++++++++++++++----------------- I don't really mind, but shouldn't the common parts be placed under net/core/ ? Like how the FIB rules have a common code in net/core/fib_rules.c ? > net/ipv6/route.c | 21 ++++------------- > 3 files changed, 48 insertions(+), 37 deletions(-)
Powered by blists - more mailing lists