summaryrefslogtreecommitdiffstats
path: root/sound/pcmcia
diff options
context:
space:
mode:
authorWei Yongjun <yjwei@cn.fujitsu.com>2008-09-05 02:55:26 +0200
committerVlad Yasevich <vladislav.yasevich@hp.com>2008-10-01 17:34:16 +0200
commit536428a9b9a98495f7ea54ad95cad83e22f1d47d (patch)
treea4a38e61207bf6144945cc5bf23cc78c8fa3bbb4 /sound/pcmcia
parentsctp: try harder to figure out address family when checking wildcards (diff)
downloadlinux-536428a9b9a98495f7ea54ad95cad83e22f1d47d.tar.xz
linux-536428a9b9a98495f7ea54ad95cad83e22f1d47d.zip
sctp: Fix to start T5-shutdown-guard timer while enter SHUTDOWN-SENT state
RFC 4960: Section 9.2 The sender of the SHUTDOWN MAY also start an overall guard timer 'T5-shutdown-guard' to bound the overall time for the shutdown sequence. At the expiration of this timer, the sender SHOULD abort the association by sending an ABORT chunk. If the 'T5-shutdown- guard' timer is used, it SHOULD be set to the recommended value of 5 times 'RTO.Max'. The timer 'T5-shutdown-guard' is used to counter the overall time for shutdown sequence, and it's start by the sender of the SHUTDOWN. So timer 'T5-shutdown-guard' should be start when we send the first SHUTDOWN chunk and enter the SHUTDOWN-SENT state, not start when we receipt of the SHUTDOWN primitive and enter SHUTDOWN-PENDING state. If 'T5-shutdown-guard' timer is start at SHUTDOWN-PENDING state, the association may be ABORT while data is still transmitting. Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com> Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
Diffstat (limited to 'sound/pcmcia')
0 files changed, 0 insertions, 0 deletions