summaryrefslogtreecommitdiff
path: root/drivers/net/phy/qsemi.c
diff options
context:
space:
mode:
authorzheng li <james.z.li@ericsson.com>2016-12-12 09:56:05 +0800
committerDavid S. Miller <davem@davemloft.net>2016-12-20 10:45:22 -0500
commit0a28cfd51e17f4f0a056bcf66bfbe492c3b99f38 (patch)
treed287b44d8adb46fdf802ee45d7945e6d41c33125 /drivers/net/phy/qsemi.c
parentad688cdbb076833ba17fc65591cd0fe01900a5cf (diff)
ipv4: Should use consistent conditional judgement for ip fragment in __ip_append_data and ip_finish_output
There is an inconsistent conditional judgement in __ip_append_data and ip_finish_output functions, the variable length in __ip_append_data just include the length of application's payload and udp header, don't include the length of ip header, but in ip_finish_output use (skb->len > ip_skb_dst_mtu(skb)) as judgement, and skb->len include the length of ip header. That causes some particular application's udp payload whose length is between (MTU - IP Header) and MTU were fragmented by ip_fragment even though the rst->dev support UFO feature. Add the length of ip header to length in __ip_append_data to keep consistent conditional judgement as ip_finish_output for ip fragment. Signed-off-by: Zheng Li <james.z.li@ericsson.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/phy/qsemi.c')
0 files changed, 0 insertions, 0 deletions