diff options
| author | Neal Cardwell <ncardwell@google.com> | 2015-04-01 20:26:46 -0400 |
|---|---|---|
| committer | Jiri Slaby <jslaby@suse.cz> | 2015-04-27 10:53:41 +0200 |
| commit | d170fbc221539c90d48fa4163f141ad948fb6c2c (patch) | |
| tree | 59ccc477b682cb8cc6921bbee0ff683aea257df2 /net/ipv4/tcp_output.c | |
| parent | ac12ff18b11259e10c2d543aa58c73ff88a68e77 (diff) | |
tcp: fix FRTO undo on cumulative ACK of SACKed range
[ Upstream commit 666b805150efd62f05810ff0db08f44a2370c937 ]
On processing cumulative ACKs, the FRTO code was not checking the
SACKed bit, meaning that there could be a spurious FRTO undo on a
cumulative ACK of a previously SACKed skb.
The FRTO code should only consider a cumulative ACK to indicate that
an original/unretransmitted skb is newly ACKed if the skb was not yet
SACKed.
The effect of the spurious FRTO undo would typically be to make the
connection think that all previously-sent packets were in flight when
they really weren't, leading to a stall and an RTO.
Signed-off-by: Neal Cardwell <ncardwell@google.com>
Signed-off-by: Yuchung Cheng <ycheng@google.com>
Fixes: e33099f96d99c ("tcp: implement RFC5682 F-RTO")
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Diffstat (limited to 'net/ipv4/tcp_output.c')
0 files changed, 0 insertions, 0 deletions