aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb
diff options
context:
space:
mode:
authorEric Dumazet <[email protected]>2019-09-26 15:42:51 -0700
committerDavid S. Miller <[email protected]>2019-09-27 20:42:24 +0200
commita41e8a88b06ee39fad4cb4a8ccf822563560a89c (patch)
tree4cb7c743f2425c421a5604ae6232843a4055c949 /scripts/gdb
parent174e23810cd3183dc2ca3f5166ef965a55eaaf54 (diff)
tcp: better handle TCP_USER_TIMEOUT in SYN_SENT state
Yuchung Cheng and Marek Majkowski independently reported a weird behavior of TCP_USER_TIMEOUT option when used at connect() time. When the TCP_USER_TIMEOUT is reached, tcp_write_timeout() believes the flow should live, and the following condition in tcp_clamp_rto_to_user_timeout() programs one jiffie timers : remaining = icsk->icsk_user_timeout - elapsed; if (remaining <= 0) return 1; /* user timeout has passed; fire ASAP */ This silly situation ends when the max syn rtx count is reached. This patch makes sure we honor both TCP_SYNCNT and TCP_USER_TIMEOUT, avoiding these spurious SYN packets. Fixes: b701a99e431d ("tcp: Add tcp_clamp_rto_to_user_timeout() helper to improve accuracy") Signed-off-by: Eric Dumazet <[email protected]> Reported-by: Yuchung Cheng <[email protected]> Reported-by: Marek Majkowski <[email protected]> Cc: Jon Maxwell <[email protected]> Link: https://marc.info/?l=linux-netdev&m=156940118307949&w=2 Acked-by: Jon Maxwell <[email protected]> Tested-by: Marek Majkowski <[email protected]> Signed-off-by: Marek Majkowski <[email protected]> Acked-by: Yuchung Cheng <[email protected]> Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'scripts/gdb')
0 files changed, 0 insertions, 0 deletions