netdev - Re: [RFC v2 PATCH 07/11] ipv6: Move dst->from into struct rt6

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: <1509475625.3828.34.camel@edumazet-glaptop3.roam.corp.google.com>
Date:   Tue, 31 Oct 2017 11:47:05 -0700
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     "David S. Miller" <davem@...emloft.net>
Cc:     netdev@...r.kernel.org
Subject: Re: [RFC v2 PATCH 07/11] ipv6: Move dst->from into struct rt6_info.

On Tue, 2017-10-31 at 23:10 +0900, David S. Miller wrote:
> The dst->from value is only used by ipv6 routes to track where
> a route "came from".
> 
> Any time we clone or copy a core ipv6 route in the ipv6 routing
> tables, we have the copy/clone's ->from point to the base route.
> 
> This is used to handle route expiration properly.
> 
> Only ipv6 uses this mechanism, and only ipv6 code references
> it.  So it is safe to move it into rt6_info.
> 
> Signed-off-by: David S. Miller <davem@...emloft.net>
> ---

Reviewed-by: Eric Dumazet <edumazet@...gle.com>