diff options
author | Herbert Xu <herbert@gondor.apana.org.au> | 2005-08-17 07:43:40 +0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2005-08-17 07:43:40 +0400 |
commit | c8ac37746489f05a32a958b048f29ae45487e81e (patch) | |
tree | c1d326c64fca3f5902438160b7b28e178318c8be /net/ipv6/ip6_input.c | |
parent | 793245eeb97bd28e363f2b0f2e766fdbff0c9619 (diff) | |
download | linux-c8ac37746489f05a32a958b048f29ae45487e81e.tar.xz |
[TCP]: Fix bug #5070: kernel BUG at net/ipv4/tcp_output.c:864
1) We send out a normal sized packet with TSO on to start off.
2) ICMP is received indicating a smaller MTU.
3) We send the current sk_send_head which needs to be fragmented
since it was created before the ICMP event. The first fragment
is then sent out.
At this point the remaining fragment is allocated by tcp_fragment.
However, its size is padded to fit the L1 cache-line size therefore
creating tail-room up to 124 bytes long.
This fragment will also be sitting at sk_send_head.
4) tcp_sendmsg is called again and it stores data in the tail-room of
of the fragment.
5) tcp_push_one is called by tcp_sendmsg which then calls tso_fragment
since the packet as a whole exceeds the MTU.
At this point we have a packet that has data in the head area being
fed to tso_fragment which bombs out.
My take on this is that we shouldn't ever call tcp_fragment on a TSO
socket for a packet that is yet to be transmitted since this creates
a packet on sk_send_head that cannot be extended.
So here is a patch to change it so that tso_fragment is always used
in this case.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv6/ip6_input.c')
0 files changed, 0 insertions, 0 deletions