netdev - Re: [PATCH net-next 1/2] net: track link status of ipv6 nexthops

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 10 Aug 2015 10:54:00 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	gospo@...ulusnetworks.com
Cc:	netdev@...r.kernel.org, ddutt@...ulusnetworks.com
Subject: Re: [PATCH net-next 1/2] net: track link status of ipv6 nexthops

From: Andy Gospodarek <gospo@...ulusnetworks.com>
Date: Thu,  6 Aug 2015 11:42:33 -0400

> Add support to track current link status of ipv6 nexthops to match
> recent changes that added support for ipv4 nexthops.  There was not a
> field already available that could track these and no space available in
> the existing rt6i_flags field, so this patch adds rt6i_nhflags to struct
> rt6_info.
> 
> Signed-off-by: Andy Gospodarek <gospo@...ulusnetworks.com>
> Signed-off-by: Dinesh Dutt <ddutt@...ulusnetworks.com>

This doesn't really make any sense to me.

You can evaluate the state of the link at the time you look at the
route at all of the places where it matters as far as I can tell.

It's so expensive to walk the entire routing table every time a link
goes up and down, so it's much better to take an "evaluate as needed"
approach to implementing this.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html