Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1545218
| From | David Miller <davem@davemloft.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2] ipv4: Should use consistent conditional judgement for ip fragment in __ip_append_data and ip_finish_output |
| Date | 2016-12-20 16:50 +0100 |
| Message-ID | <sQuPT-7q6-13@gated-at.bofh.it> (permalink) |
| References | <sNo4i-6w8-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
From: Zheng Li <lizheng043@gmail.com> Date: Mon, 12 Dec 2016 09:56:05 +0800 > From: zheng li <james.z.li@ericsson.com> > > 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> Applied, thanks.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH v2] ipv4: Should use consistent conditional judgement for ip fragment in __ip_append_data and ip_finish_output Zheng Li <lizheng043@gmail.com> - 2016-12-12 03:00 +0100 Re: [PATCH v2] ipv4: Should use consistent conditional judgement for ip fragment in __ip_append_data and ip_finish_output David Miller <davem@davemloft.net> - 2016-12-20 16:50 +0100
csiph-web