tcp: use SACKs and DSACKs that arrive on ACKs below snd_una
authorNeal Cardwell <ncardwell@google.com>
Wed, 16 Nov 2011 08:58:03 +0000 (08:58 +0000)
committerDavid S. Miller <davem@davemloft.net>
Sun, 27 Nov 2011 23:54:09 +0000 (18:54 -0500)
commite95ae2f2cf10f7bf27b492aa6188f3cd745de162
tree2808047891b1c8e3eae559c55d09a5cfeef79fdb
parent5628adf1a0ff39b9e76e1a8e1c94dadabfd46914
tcp: use SACKs and DSACKs that arrive on ACKs below snd_una

The bug: When the ACK field is below snd_una (which can happen when
ACKs are reordered), senders ignored DSACKs (preventing undo) and did
not call tcp_fastretrans_alert, so they did not increment
prr_delivered to reflect newly-SACKed sequence ranges, and did not
call tcp_xmit_retransmit_queue, thus passing up chances to send out
more retransmitted and new packets based on any newly-SACKed packets.

The change: When the ACK field is below snd_una (the "old_ack" goto
label), call tcp_fastretrans_alert to allow undo based on any
newly-arrived DSACKs and try to send out more packets based on
newly-SACKed packets.

Other patches in this series will provide other changes that are
necessary to fully fix this problem.

Signed-off-by: Neal Cardwell <ncardwell@google.com>
Acked-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/tcp_input.c