netdev - Re: [PATCH net-next 6/9] ipv6: Handle route deletion notification

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]

Date:   Tue, 24 Dec 2019 10:03:00 -0700
From:   David Ahern <dsahern@...il.com>
To:     Ido Schimmel <idosch@...sch.org>, netdev@...r.kernel.org
Cc:     davem@...emloft.net, roopa@...ulusnetworks.com,
        jakub.kicinski@...ronome.com, jiri@...lanox.com,
        Ido Schimmel <idosch@...lanox.com>
Subject: Re: [PATCH net-next 6/9] ipv6: Handle route deletion notification

On 12/23/19 6:28 AM, Ido Schimmel wrote:
> From: Ido Schimmel <idosch@...lanox.com>
> 
> For the purpose of route offload, when a single route is deleted, it is
> only of interest if it is the first route in the node or if it is
> sibling to such a route.
> 
> In the first case, distinguish between several possibilities:
> 
> 1. Route is the last route in the node. Emit a delete notification
> 
> 2. Route is followed by a non-multipath route. Emit a replace
> notification for the non-multipath route.
> 
> 3. Route is followed by a multipath route. Emit a replace notification
> for the multipath route.
> 
> In the second case, only emit a delete notification to ensure the route
> is no longer used as a valid nexthop.
> 
> Signed-off-by: Ido Schimmel <idosch@...lanox.com>
> Reviewed-by: Jiri Pirko <jiri@...lanox.com>
> ---
>  include/net/ip6_fib.h |  1 +
>  net/ipv6/ip6_fib.c    | 44 ++++++++++++++++++++++++++++++++++++++++++-
>  2 files changed, 44 insertions(+), 1 deletion(-)
> 

Reviewed-by: David Ahern <dsahern@...il.com>