netdev - Re: [PATCH net-next 00/18] ipv6: Align nexthop behaviour with IPv4

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] [day] [month] [year] [list]

Message-ID: <a6a861ee-06a0-ef3c-66de-611e30a63a21@gmail.com>
Date:   Tue, 9 Jan 2018 21:41:11 -0700
From:   David Ahern <dsahern@...il.com>
To:     Ido Schimmel <idosch@...sch.org>
Cc:     Ido Schimmel <idosch@...lanox.com>, netdev@...r.kernel.org,
        davem@...emloft.net, roopa@...ulusnetworks.com,
        nicolas.dichtel@...nd.com, weiwan@...gle.com, kafai@...com,
        yoshfuji@...ux-ipv6.org, mlxsw@...lanox.com
Subject: Re: [PATCH net-next 00/18] ipv6: Align nexthop behaviour with IPv4

On 1/9/18 1:04 AM, Ido Schimmel wrote:
> On Sun, Jan 07, 2018 at 10:20:11AM -0700, David Ahern wrote:
>> One of many follow on changes that would be beneficial is to remove the
>> idev dereference in the hot path to check the
>> ignore_routes_with_linkdown sysctl.
> 
> When a netdev loses its carrier we can set the RTNH_F_DEAD flag for all
> the nexthops using it as their nexthop device, in case the sysctl is
> set. Similarly, when the sysctl is toggled we can walk the routing
> tables and toggle the flag where appropriate.
> 
> You have a different idea?

that would work.