sctp: Process OOTB ASCONF/ASCONF-ACK Chunk at CLOSED
Subsystems (2)
RFC5061 said that If the received ASCONF Chunk is not associated with any association, the Chunk should be treated as OOTB. Do the same thing for received ASCONF-ACK Chunk.
So, process OOTB ASCONF/ASCONF-ACK Chunk according to section 8.4 of RFC4960.
Signed-off-by Shan Wei <[email protected]>
---
v1-v2: Treat ASCONF-ACK chunk as OOTB chunk for no association.
--- net/sctp/sm_statetable.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
net/sctp/sm_statetable.c +2 -2
@@ -449,7 +449,7 @@ static const sctp_sm_table_entry_t chunk_event_table[SCTP_NUM_BASE_CHUNK_TYPES][/* SCTP_STATE_EMPTY */ \TYPE_SCTP_FUNC (sctp_sf_ootb), \/* SCTP_STATE_CLOSED */ \ -TYPE_SCTP_FUNC (sctp_sf_discard_chunk), \ +TYPE_SCTP_FUNC (sctp_sf_ootb), \/* SCTP_STATE_COOKIE_WAIT */ \ TYPE_SCTP_FUNC(sctp_sf_discard_chunk), \/* SCTP_STATE_COOKIE_ECHOED */ \
@@ -470,7 +470,7 @@ static const sctp_sm_table_entry_t chunk_event_table[SCTP_NUM_BASE_CHUNK_TYPES][/* SCTP_STATE_EMPTY */ \TYPE_SCTP_FUNC (sctp_sf_ootb), \/* SCTP_STATE_CLOSED */ \ -TYPE_SCTP_FUNC (sctp_sf_discard_chunk), \ +TYPE_SCTP_FUNC (sctp_sf_ootb), \/* SCTP_STATE_COOKIE_WAIT */ \ TYPE_SCTP_FUNC(sctp_sf_discard_chunk), \/* SCTP_STATE_COOKIE_ECHOED */ \
Signature · 1 line
1.6.3.3