]> git.karo-electronics.de Git - karo-tx-linux.git/commit
tcp: reset timer after any SYNACK retransmit
authorYuchung Cheng <ycheng@google.com>
Mon, 29 Apr 2013 08:44:51 +0000 (08:44 +0000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 19 May 2013 18:38:34 +0000 (11:38 -0700)
commita1d9ddb105801c4ac651314f5963ed2de45fc494
treefc4f3eee6e39563c3c99da3540137027dad342db
parent0523cdce095dfa615f9c7308603bb11e99179e3c
tcp: reset timer after any SYNACK retransmit

[ Upstream commit cd75eff64dae8856afbf6ef0f0ca3c145465d8e0 ]

Linux immediately returns SYNACK on (spurious) SYN retransmits, but
keeps the SYNACK timer running independently. Thus the timer may
fire right after the SYNACK retransmit and causes a SYN-SYNACK
cross-fire burst.

Adopt the fast retransmit/recovery idea in established state by
re-arming the SYNACK timer after the fast (SYNACK) retransmit. The
timer may fire late up to 500ms due to the current SYNACK timer wheel,
but it's OK to be conservative when network is congested. Eric's new
listener design should address this issue.

Signed-off-by: Yuchung Cheng <ycheng@google.com>
Acked-by: Eric Dumazet <edumazet@google.com>
Acked-by: Neal Cardwell <ncardwell@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
net/ipv4/tcp_minisocks.c