netdev - Re: [PATCH net-next 4/4] net, neigh: Add NTF_MANAGED flag for managed neighbor entries

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: <YWauH/k8tfuLzsU5@shredder>
Date:   Wed, 13 Oct 2021 12:59:59 +0300
From:   Ido Schimmel <idosch@...sch.org>
To:     Daniel Borkmann <daniel@...earbox.net>
Cc:     davem@...emloft.net, kuba@...nel.org, roopa@...dia.com,
        dsahern@...nel.org, m@...bda.lt, john.fastabend@...il.com,
        netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: [PATCH net-next 4/4] net, neigh: Add NTF_MANAGED flag for
 managed neighbor entries

On Wed, Oct 13, 2021 at 11:26:50AM +0200, Daniel Borkmann wrote:
> On 10/12/21 6:31 PM, Ido Schimmel wrote:
> > In our HW the nexthop table is squashed together with the neighbour
> > table, so that it provides {netdev, MAC} and not {netdev, IP} with which
> > the kernel performs another lookup in its neighbour table. We want to
> > avoid situations where we perform multipathing between valid and failed
> > nexthop (basically, fib_multipath_use_neigh=1), so we only program valid
> > nexthop. But it means that nothing will trigger the resolution of the
> > failed nexthops, thus the need to probe the neighbours.
> 
> Makes sense. Given you have the setup/HW, if you have a chance to consolidate
> the mlxsw logic with the new NTF_MANAGED entries, that would be awesome!

Yes, I will take care of that