ipv6: Should use consistent conditional judgement for ip6 fragment between __ip6_appe...
authorZheng Li <james.z.li@ericsson.com>
Wed, 28 Dec 2016 15:23:46 +0000 (23:23 +0800)
committerDavid S. Miller <davem@davemloft.net>
Thu, 29 Dec 2016 16:55:17 +0000 (11:55 -0500)
commite4c5e13aa45c23692e4acf56f0b3533f328199b2
tree4ddeeaefcd95580c777f22822f3ae6fa7678a94f
parent60133867f1f111aaf3a8c00375b8026142a9a591
ipv6: Should use consistent conditional judgement for ip6 fragment between __ip6_append_data and ip6_finish_output

There is an inconsistent conditional judgement between __ip6_append_data
and ip6_finish_output functions, the variable length in __ip6_append_data
just include the length of application's payload and udp6 header, don't
include the length of ipv6 header, but in ip6_finish_output use
(skb->len > ip6_skb_dst_mtu(skb)) as judgement, and skb->len include the
length of ipv6 header.

That causes some particular application's udp6 payloads whose length are
between (MTU - IPv6 Header) and MTU were fragmented by ip6_fragment even
though the rst->dev support UFO feature.

Add the length of ipv6 header to length in __ip6_append_data to keep
consistent conditional judgement as ip6_finish_output for ip6 fragment.

Signed-off-by: Zheng Li <james.z.li@ericsson.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv6/ip6_output.c