[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160531.113913.1477085966766110028.davem@davemloft.net>
Date: Tue, 31 May 2016 11:39:13 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: alan.davey@...aswitch.com
Cc: netdev@...r.kernel.org, kuznet@....inr.ac.ru, jmorris@...ei.org,
yoshfuji@...ux-ipv6.org, kaber@...sh.net
Subject: Re: [PATCH] net: Fragment large datagrams even when IP_HDRINCL is
set.
From: Alan Davey <alan.davey@...aswitch.com>
Date: Mon, 23 May 2016 15:23:45 +0100
> One of the bugs documented in the raw(7) man page is as follows: When the
> IP_HDRINCL option is set, datagrams will not be fragmented and are limited to
> the interface MTU.
>
> This patch fixes the bug by removing the check for "length > rt->dst.dev->mtu"
> in raw_send_hdrinc() (net/ipv4/raw.c). Datagrams are no longer limited to the
> interface MTU size if the IP_HDRINCL option is set, but are fragmented, if
> necessary, in the same way as all other datagrams.
>
> Signed-off-by: Alan Davey <alan.davey@...aswitch.com>
This is not a bug, it's a feature and it's how RAW ipv4 sockets have behaved
for two decades.
If the user wants to use hdr inclusion, he can send multiple frames and set
the fragmentation bits appropriately.
I'm not applying this patch.
Powered by blists - more mailing lists