netdev - Re: [PATCH] net: ip_finish_output_gso: If skb_gso_network_seglen exceeds MTU, allow segmentation for gre tunneled skbs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 12 Aug 2016 08:18:00 +0300
From:	Shmulik Ladkani <shmulik.ladkani@...il.com>
To:	wenxu <wenxu@...oud.cn>
Cc:	David Miller <davem@...emloft.net>, kuznet@....inr.ac.ru,
	jmorris@...ei.org, kaber@...sh.net, yoshfuji@...ux-ipv6.org,
	netdev@...r.kernel.org, wenx05124561@....com,
	hannes@...essinduktion.org
Subject: Re: [PATCH] net: ip_finish_output_gso: If skb_gso_network_seglen
 exceeds MTU, allow segmentation for gre tunneled skbs

Hi,

On Fri, 12 Aug 2016 11:51:07 +0800 wenxu <wenxu@...oud.cn> wrote:
> 
> And in b8247f095edd, the condition skb_iif also should be removed.
> given:
>      ovs-internal-dev bridge with ovs-gre
> 
> There are the same problem which the skb from local.

There's no need to remove the skb_iif criteria:

For the local bridge port, we have control over its mtu. This allows
setting an mtu value that takes into account the gre encapsulation
performed by other member ports.
By doing so, locally generated traffic (on br0) will have a proper
gso_size.

OTOH if packet arrives from an ingress member port (such as tap0) the
packet's gso_size could have been set by another system - which is not
always under our control.

( see discussion in http://www.spinics.net/lists/netdev/msg385085.html )

Regards,
Shmulik