diff options
| author | Vlad Yasevich <vladislav.yasevich@hp.com> | 2009-01-22 14:53:01 -0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2009-01-22 14:53:01 -0800 |
| commit | 759af00ebef858015eb68876ac1f383bcb6a1774 (patch) | |
| tree | 4a7b6d9ea1732f5f1e3f109faa0891d779b4522a /net/sctp/input.c | |
| parent | 6574df9a89f9f7da3a4e5cee7633d430319d3350 (diff) | |
sctp: Properly timestamp outgoing data chunks for rtx purposes
Recent changes to the retransmit code exposed a long standing
bug where it was possible for a chunk to be time stamped
after the retransmit timer was reset. This caused a rare
situation where the retrnamist timer has expired, but
nothing was marked for retrnasmission because all of
timesamps on data were less then 1 rto ago. As result,
the timer was never restarted since nothing was retransmitted,
and this resulted in a hung association that did couldn't
complete the data transfer. The solution is to timestamp
the chunk when it's added to the packet for transmission
purposes. After the packet is trsnmitted the rtx timer
is restarted. This guarantees that when the timer expires,
there will be data to retransmit.
Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/sctp/input.c')
0 files changed, 0 insertions, 0 deletions