netdev - Re: [PATCH] net: ipv4: Remove MTU check in IP

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:   Sat, 06 Jan 2018 20:41:36 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     dev.jongy@...il.com
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH] net: ipv4: Remove MTU check in IP_HDRINCL send flow

From: Yonatan Goldschmidt <dev.jongy@...il.com>
Date: Sun, 7 Jan 2018 01:26:48 +0200

> IP fragmentation can be performed as expected down the stack, without touching
> irrelevant fields in the included header besides fragment offset, setting
> IP_MF and header checksum.
> If the included header has IP_DF set, EMSGSIZE is returned.
> 
> This allows users of IP_HDRINCL to have the kernel perform fragmentation.
> 
> Signed-off-by: Yonatan Goldschmidt <dev.jongy@...il.com>

This has been brought up before and we decided that for RAW sockets
the user is responsible for fragmentation, and the kernel should not
"manage" the packet given to it in any way whatsoever.