tcp: avoid setting cwnd to invalid ssthresh after cwnd reduction states
authorYuchung Cheng <ycheng@google.com>
Tue, 1 Aug 2017 20:22:32 +0000 (13:22 -0700)
committerWilly Tarreau <w@1wt.eu>
Thu, 2 Nov 2017 06:16:23 +0000 (07:16 +0100)
commit37cb36243061666f8bd44fdc51229ca6896effa3
treeddd3a709c194abe9e696cfd2118a904e2e6157d0
parent6f85a8873040becd7d779ad5f510f1b73d04f59b
tcp: avoid setting cwnd to invalid ssthresh after cwnd reduction states

commit ed254971edea92c3ac5c67c6a05247a92aa6075e upstream.

If the sender switches the congestion control during ECN-triggered
cwnd-reduction state (CA_CWR), upon exiting recovery cwnd is set to
the ssthresh value calculated by the previous congestion control. If
the previous congestion control is BBR that always keep ssthresh
to TCP_INIFINITE_SSTHRESH, cwnd ends up being infinite. The safe
step is to avoid assigning invalid ssthresh value when recovery ends.

Signed-off-by: Yuchung Cheng <ycheng@google.com>
Signed-off-by: Neal Cardwell <ncardwell@google.com>
Acked-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Willy Tarreau <w@1wt.eu>
net/ipv4/tcp_input.c