netdev - Re: [PATCH net] ipv4: consistent reporting of pmtu data in case of corking

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:	Sun, 22 Dec 2013 18:52:34 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	hannes@...essinduktion.org
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net] ipv4: consistent reporting of pmtu data in case of
 corking

From: Hannes Frederic Sowa <hannes@...essinduktion.org>
Date: Thu, 19 Dec 2013 02:13:36 +0100

> We report different pmtu values back on the first write and on further
> writes on an corked socket.
> 
> Also don't include the dst.header_len (respectively exthdrlen) as this
> should already be dealt with by the interface mtu of the outgoing
> (virtual) interface and policy of that interface should dictate if
> fragmentation should happen.
> 
> Instead reduce the pmtu data by IP options as we do for IPv6. Make the
> same changes for ip_append_data, where we did not care about options or
> dst.header_len at all.
> 
> Signed-off-by: Hannes Frederic Sowa <hannes@...essinduktion.org>

Looks good, applied, 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