Files
linux/net/ipv4
Ilpo Järvinen 31885683c2 tcp: fix for zero packets_in_flight was too broad
[ Upstream commit 6731d2095b ]

There are transients during normal FRTO procedure during which
the packets_in_flight can go to zero between write_queue state
updates and firing the resulting segments out. As FRTO processing
occurs during that window the check must be more precise to
not match "spuriously" :-). More specificly, e.g., when
packets_in_flight is zero but FLAG_DATA_ACKED is true the problematic
branch that set cwnd into zero would not be taken and new segments
might be sent out later.

Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Tested-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>
2013-02-14 10:47:35 -08:00
..
2012-02-03 09:18:54 -08:00
2011-03-12 15:08:49 -08:00
2011-08-15 18:31:39 -07:00
2011-02-01 15:35:25 -08:00
2013-01-11 09:03:48 -08:00
2012-10-13 05:28:07 +09:00
2012-03-23 11:20:51 -07:00
2013-01-11 09:03:48 -08:00
2012-10-28 10:02:13 -07:00
2011-03-31 11:26:23 -03:00
2011-03-31 11:26:23 -03:00
2012-11-17 13:14:24 -08:00
2010-10-27 11:37:32 -07:00
2011-07-07 00:27:05 -07:00
2010-07-12 12:57:54 -07:00