aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/Kconfig
diff options
context:
space:
mode:
authorYuchung Cheng <ycheng@google.com>2014-05-30 15:25:59 -0700
committerDavid S. Miller <davem@davemloft.net>2014-06-02 16:50:49 -0700
commit0cfa5c07d6d1d7f8e710fc671c5ba1ce85e09fa4 (patch)
treea64c77549f5863019d69eb08d25b557ba6a6f5b1 /drivers/net/ethernet/Kconfig
parentnetlink: Only check file credentials for implicit destinations (diff)
downloadlinux-dev-0cfa5c07d6d1d7f8e710fc671c5ba1ce85e09fa4.tar.xz
linux-dev-0cfa5c07d6d1d7f8e710fc671c5ba1ce85e09fa4.zip
tcp: fix cwnd undo on DSACK in F-RTO
This bug is discovered by an recent F-RTO issue on tcpm list https://www.ietf.org/mail-archive/web/tcpm/current/msg08794.html The bug is that currently F-RTO does not use DSACK to undo cwnd in certain cases: upon receiving an ACK after the RTO retransmission in F-RTO, and the ACK has DSACK indicating the retransmission is spurious, the sender only calls tcp_try_undo_loss() if some never retransmisted data is sacked (FLAG_ORIG_DATA_SACKED). The correct behavior is to unconditionally call tcp_try_undo_loss so the DSACK information is used properly to undo the cwnd reduction. Signed-off-by: Yuchung Cheng <ycheng@google.com> Signed-off-by: Neal Cardwell <ncardwell@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions