diff options
author | Wei Yongjun <yjwei@cn.fujitsu.com> | 2008-10-23 10:00:49 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2008-10-23 10:00:49 +0200 |
commit | cf896d514a4564027929a6d284872c74987085ef (patch) | |
tree | f6ce180ea181798ecda37c3563816f5b029589ce /net/sctp/sm_statefuns.c | |
parent | sctp: Add check for the TSN field of the SHUTDOWN chunk (diff) | |
download | linux-cf896d514a4564027929a6d284872c74987085ef.tar.xz linux-cf896d514a4564027929a6d284872c74987085ef.zip |
sctp: Fix to handle SHUTDOWN in SHUTDOWN-PENDING state
If SHUTDOWN is received in SHUTDOWN-PENDING state, enpoint should enter
the SHUTDOWN-RECEIVED state and check the Cumulative TSN Ack field of
the SHUTDOWN chunk (RFC 4960 Section 9.2). If the SHUTDOWN chunk can
acknowledge all of the send DATA chunks, SHUTDOWN-ACK should be sent.
But now endpoint just silently discarded the SHUTDOWN chunk.
SHUTDOWN received in SHUTDOWN-PENDING state can happend when the last
SACK is lost by network, or the SHUTDOWN chunk can acknowledge all of
the received DATA chunks. The packet sequence(SACK lost) is like this:
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
<----------- DATA
<--- shutdown
Enter SHUTDOWN-PENDING state
SACK ----lost---->
SHUTDOWN(*1) ------------>
<----------- SHUTDOWN-ACK
(*1) silently discarded now.
This patch fix to handle SHUTDOWN in SHUTDOWN-PENDING state as the same
as ESTABLISHED state.
Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com>
Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/sctp/sm_statefuns.c')
0 files changed, 0 insertions, 0 deletions