diff options
| author | Zheng Li <james.z.li@ericsson.com> | 2016-12-28 23:23:46 +0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-12-29 11:55:17 -0500 |
| commit | e4c5e13aa45c23692e4acf56f0b3533f328199b2 (patch) | |
| tree | 4ddeeaefcd95580c777f22822f3ae6fa7678a94f | |
| parent | 60133867f1f111aaf3a8c00375b8026142a9a591 (diff) | |
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>