netdev - Re: [PATCH v4 net-next 1/3] ipv4: Move cached routes to fib_nh

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190430145637.GA20908@splinter>
Date:   Tue, 30 Apr 2019 17:56:37 +0300
From:   Ido Schimmel <idosch@...sch.org>
To:     David Ahern <dsahern@...nel.org>
Cc:     davem@...emloft.net, netdev@...r.kernel.org, idosch@...lanox.com,
        David Ahern <dsahern@...il.com>
Subject: Re: [PATCH v4 net-next 1/3] ipv4: Move cached routes to fib_nh_common

On Tue, Apr 30, 2019 at 07:45:48AM -0700, David Ahern wrote:
> From: David Ahern <dsahern@...il.com>
> 
> While the cached routes, nh_pcpu_rth_output and nh_rth_input, are IPv4
> specific, a later patch wants to make them accessible for IPv6 nexthops
> with IPv4 routes using a fib6_nh. Move the cached routes from fib_nh to
> fib_nh_common and update references.
> 
> Initialization of the cached entries is moved to fib_nh_common_init,
> and free is moved to fib_nh_common_release.
> 
> Change in location only, from fib_nh up to fib_nh_common; no functional
> change intended.
> 
> Signed-off-by: David Ahern <dsahern@...il.com>

Reviewed-by: Ido Schimmel <idosch@...lanox.com>