Re: [PATCH] tcp: frto should not set snd_cwnd to 0

[David Miller <davem@davemloft.net>]

From: Pasi Kärkkäinen <pasik@iki.fi>
Date: Wed, 6 Feb 2013 23:13:43 +0200

> On Wed, Feb 06, 2013 at 03:55:04PM -0500, David Miller wrote:
>> From: Neal Cardwell <ncardwell@google.com>
>> Date: Tue, 5 Feb 2013 14:49:04 -0500
>> 
>> > On Mon, Feb 4, 2013 at 7:14 AM, Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> wrote:
>> >> [PATCH 1/1] tcp: fix for zero packets_in_flight was too broad
>> >>
>> >> 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.
>> >>
>> >> Only compile tested.
>> >>
>> >> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
>>  ...
>> > Acked-by: Neal Cardwell <ncardwell@google.com>
>> 
>> Applied, thanks everyone.
>>
> 
> Hmm.. are we missing CC stable@kernel.org in these patches? 
> I guess 3.6.x is already EOL, but it'd be nice to get this bug fixed also in 3.7.x ..

We never CC: stable on networking patches, I queue them up manually
and submit them at a time of my own choosing.