netdev - Re: [PATCH net-next] ipv4: raise IP_MAX

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]

Date:	Tue, 20 Aug 2013 15:08:23 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	netdev@...r.kernel.org, willemb@...gle.com, kuznet@....inr.ac.ru
Subject: Re: [PATCH net-next] ipv4: raise IP_MAX_MTU to theoretical limit

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Sun, 18 Aug 2013 19:08:07 -0700

> From: Eric Dumazet <edumazet@...gle.com>
> 
> As discussed last year [1], there is no compelling reason
> to limit IPv4 MTU to 0xFFF0, while real limit is 0xFFFF
> 
> [1] : http://marc.info/?l=linux-netdev&m=135607247609434&w=2
> 
> Willem raised this issue again because some of our internal
> regression tests broke after lo mtu being set to 65536.
> 
> IP_MTU reports 0xFFF0, and the test attempts to send a RAW datagram of
> mtu + 1 bytes, expecting the send() to fail, but it does not.
> 
> Alexey raised interesting points about TCP MSS, that should be addressed
> in follow-up patches in TCP stack if needed, as someone could also set
> an odd mtu anyway.
> 
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>

Applied, thanks for following through on this Eric.
--
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