SCTP: properly clean up fragment and ordering queues during FWD-TSN.

When we recieve a FWD-TSN (meaning the peer has abandoned the data),
we need to clean up any partially received messages that may be
hanging out on the re-assembly or re-ordering queues.  This is
a MUST requirement that was not properly done before.

Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com.>

1 files changed, 3 insertions, 0 deletions

diff --git a/net/sctp/sm_sideeffect.c b/net/sctp/sm_sideeffect.c
index d9fad4f6ffc3..1907318e70f1 100644
--- a/net/sctp/sm_sideeffect.c
+++ b/net/sctp/sm_sideeffect.c
@@ -1130,6 +1130,9 @@ static int sctp_cmd_interpreter(sctp_event_t event_type,
                         /* Move the Cumulattive TSN Ack ahead. */
                         sctp_tsnmap_skip(&asoc->peer.tsn_map, cmd->obj.u32);
 
+                        /* purge the fragmentation queue */
+                        sctp_ulpq_reasm_flushtsn(&asoc->ulpq, cmd->obj.u32);
+
                         /* Abort any in progress partial delivery. */
                         sctp_ulpq_abort_pd(&asoc->ulpq, GFP_ATOMIC);
                         break;