aboutsummaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorEric Dumazet <eric.dumazet@gmail.com>2012-03-10 09:20:21 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-03-23 11:20:51 -0700
commit137a954db947096bd9378ff5a6a77336231f4a90 (patch)
treeaaf7ac40505fa71197cf994cbe7a454b74bbea60 /fs
parent2f54cf2cb91a3efadeaae555baed47eac660d53c (diff)
downloadkernel_samsung_crespo-137a954db947096bd9378ff5a6a77336231f4a90.zip
kernel_samsung_crespo-137a954db947096bd9378ff5a6a77336231f4a90.tar.gz
kernel_samsung_crespo-137a954db947096bd9378ff5a6a77336231f4a90.tar.bz2
tcp: fix syncookie regression
[ Upstream commit dfd25ffffc132c00070eed64200e8950da5d7e9d ] commit ea4fc0d619 (ipv4: Don't use rt->rt_{src,dst} in ip_queue_xmit()) added a serious regression on synflood handling. Simon Kirby discovered a successful connection was delayed by 20 seconds before being responsive. In my tests, I discovered that xmit frames were lost, and needed ~4 retransmits and a socket dst rebuild before being really sent. In case of syncookie initiated connection, we use a different path to initialize the socket dst, and inet->cork.fl.u.ip4 is left cleared. As ip_queue_xmit() now depends on inet flow being setup, fix this by copying the temp flowi4 we use in cookie_v4_check(). Reported-by: Simon Kirby <sim@netnation.com> Bisected-by: Simon Kirby <sim@netnation.com> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com> Tested-by: Eric Dumazet <eric.dumazet@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions