netdev - Re: [PATCH net] ipv6: Allow IPv4-mapped address as next-hop

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: <20161130.105857.656098579060491142.davem@davemloft.net>
Date:   Wed, 30 Nov 2016 10:58:57 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     nordmark@...sta.com
Cc:     kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org,
        kaber@...sh.net, netdev@...r.kernel.org, gilligan@...sta.com
Subject: Re: [PATCH net] ipv6: Allow IPv4-mapped address as next-hop

From: Erik Nordmark <nordmark@...sta.com>
Date: Mon, 28 Nov 2016 15:27:05 -0800

> @@ -1995,8 +1995,11 @@ static struct rt6_info *ip6_route_info_c
>  			   It is very good, but in some (rare!) circumstances
>  			   (SIT, PtP, NBMA NOARP links) it is handy to allow
>  			   some exceptions. --ANK
> + We allow IPv4-mapped nexthops to support RFC4798-type
> +			   addressing
>  			 */

This is definitely not indented and formatted correctly, please fix.