netdev - Re: [RFC v2 PATCH 08/11] xfrm: Move dst->path into struct xfrm

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: <1509475745.3828.35.camel@edumazet-glaptop3.roam.corp.google.com>
Date:   Tue, 31 Oct 2017 11:49: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 08/11] xfrm: Move dst->path into struct xfrm_dst

On Tue, 2017-10-31 at 23:10 +0900, David S. Miller wrote:
> The first member of an IPSEC route bundle chain sets it's dst->path to
> the underlying ipv4/ipv6 route that carries the bundle.
> 
> Stated another way, if one were to follow the xfrm_dst->child chain of
> the bundle, the final non-NULL pointer would be the path and point to
> either an ipv4 or an ipv6 route.
> 
> This is largely used to make sure that PMTU events propagate down to
> the correct ipv4 or ipv6 route.
> 
> When we don't have the top of an IPSEC bundle 'dst->path == dst'.
> 
> Move it down into xfrm_dst and key off of dst->xfrm.
> 
> Signed-off-by: David S. Miller <davem@...emloft.net>
> ---

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