| commit | e533ca16f31f9e5abfaf5d8c7dbe7095f01474b6 | |
| author | Vlad Yasevich <vladislav.yasevich@hp.com> | |
| Tue, 30 Jan 2007 22:36:14 +0000 (30 14:36 -0800) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Tue, 30 Jan 2007 22:36:14 +0000 (30 14:36 -0800) | ||
| tree | ac08e7242f36a9273488325c652629373cf277c2 | treesnapshot (tar.gz zip) |
| parent | 29556526b970c2e7d4ca808b6082c33981adfdff | commitdiff |
[SCTP]: Force update of the rto when processing HB-ACK
When processing a HEARTBEAT-ACK it's possible that the transport rto
timers will not be updated because a prior T3-RTX processing would
have cleared the rto_pending flag on the transport. However, if
we received a valid HEARTBEAT-ACK, we want to force update the
rto variables, so re-set the rto_pending flag before calling
sctp_transport_update_rto().
Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
Signed-off-by: Sridhar Samudrala <sri@us.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
When processing a HEARTBEAT-ACK it's possible that the transport rto
timers will not be updated because a prior T3-RTX processing would
have cleared the rto_pending flag on the transport. However, if
we received a valid HEARTBEAT-ACK, we want to force update the
rto variables, so re-set the rto_pending flag before calling
sctp_transport_update_rto().
Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
Signed-off-by: Sridhar Samudrala <sri@us.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
| net/sctp/sm_sideeffect.c | diffblobblamehistory |