netdev - Re: [PATCH net-next] ipv6: use interface mtu for determining if packet-too-big should be send

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: <1387201782.19078.230.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Mon, 16 Dec 2013 05:49:42 -0800
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Hannes Frederic Sowa <hannes@...essinduktion.org>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] ipv6: use interface mtu for determining if
 packet-too-big should be send

On Mon, 2013-12-16 at 09:09 +0100, Hannes Frederic Sowa wrote:
> IPv6 forwarding path should also not depend on the path mtu values to
> judge if a packet should get dropped and an ICMP PTB should be returned.
> 
> For the accompanying change in IPv4, have a look at "ipv4: introduce
> ip_dst_mtu_secure and protect forwarding path against pmtu spoofing".
> 

No commit sha1 (truncated to 12 digits) ?

> I needed to move in6_dev_dev around to keep ip6_dst_mtu_secure as a static
> inline function in the header and to keep header dependencies happy.
> 
> For the IPv4 change, see patch "ipv4: introduce ip_dst_mtu_secure and
> protect forwarding path against pmtu spoofing".

Redundant sentence ?

And no documentation for the new setting.

git grep -n forward_use_pmtu Documentation

Thanks


--
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