netdev - RE: GRO issue with kernel 3.4.94 (icmp fragmentation needed)

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:	Fri, 27 Jun 2014 19:07:25 +0900
From:	"jungwon park" <jwpark2@...tecode.co.kr>
To:	"'Florian Westphal'" <fw@...len.de>
Cc:	<netdev@...r.kernel.org>
Subject: RE: GRO issue with kernel 3.4.94 (icmp fragmentation needed)

Good!
When I apply the patch(ipv4: set transport header earlier), there is no
problem.
Thanks, Florian.

-----Original Message-----
From: Florian Westphal [mailto:fw@...len.de] 
Sent: Friday, June 27, 2014 6:05 PM
To: jungwon park
Cc: netdev@...r.kernel.org
Subject: Re: GRO issue with kernel 3.4.94 (icmp fragmentation needed)

jungwon park <jwpark2@...tecode.co.kr> wrote:
> When using the linux router is turned on GRO, router send the 
> 'fragmentation needed' packets to the sender.

Indeed 8-(

> When I turned off GRO, the router operate normally, and there is no
problem.
> and with 3.4.91 kernel, the router has no problem.
> 
> I doubt 'ipv4: ip_forward: fix inverted local_df test' patch.
> (http://patchwork.ozlabs.org/patch/345509/)
> When I revert this patch, the router has no problem.

Can you please cherry-pick following patch on top of vanilla 3.4.92?
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2
1d1196a35f5686c4323e42a62fdb4b23b0ab4a3

commit 21d1196a35f5686c4323e42a62fdb4b23b0ab4a3
Author: Eric Dumazet <edumazet@...gle.com>
ipv4: set transport header earlier

I think that should fix this bug, it should apply cleanly on top of 3.4.y
tree.

[ patch is in 3.11, also backported to 3.10.y tree ]

The problem is that, when dealing with GRO packets, we try to determine the
size of the individual packets.  To do this, we rely on the transport
header.

Unfortunately the transport header is not set for the forward path in 3.4,
so we look at the network header instead.

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