diff options
author | Neal Cardwell <ncardwell@google.com> | 2012-02-12 18:37:10 +0000 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-02-29 16:34:16 -0800 |
commit | dd31c1ce7ef7b363215081fde02f13bf3e50b5a1 (patch) | |
tree | 8080df1b00e528814195a69f24fd6508d0554623 /net/ipv4/xfrm4_input.c | |
parent | 382e8f84cb3db5295aa2f142a11e42eac6544ab4 (diff) | |
download | kernel_samsung_aries-dd31c1ce7ef7b363215081fde02f13bf3e50b5a1.zip kernel_samsung_aries-dd31c1ce7ef7b363215081fde02f13bf3e50b5a1.tar.gz kernel_samsung_aries-dd31c1ce7ef7b363215081fde02f13bf3e50b5a1.tar.bz2 |
tcp: fix range tcp_shifted_skb() passes to tcp_sacktag_one()
[ Upstream commit daef52bab1fd26e24e8e9578f8fb33ba1d0cb412 ]
Fix the newly-SACKed range to be the range of newly-shifted bytes.
Previously - since 832d11c5cd076abc0aa1eaf7be96c81d1a59ce41 -
tcp_shifted_skb() incorrectly called tcp_sacktag_one() with the start
and end sequence numbers of the skb it passes in set to the range just
beyond the range that is newly-SACKed.
This commit also removes a special-case adjustment to lost_cnt_hint in
tcp_shifted_skb() since the pre-existing adjustment of lost_cnt_hint
in tcp_sacktag_one() now properly handles this things now that the
correct start sequence number is passed in.
Signed-off-by: Neal Cardwell <ncardwell@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/ipv4/xfrm4_input.c')
0 files changed, 0 insertions, 0 deletions