sctp: Correctly implement Fast Recovery cwnd manipulations.

Correctly keep track of Fast Recovery state and do not reduce
congestion window multiple times during sucht state.

Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
Tested-by: Wei Yongjun <yjwei@cn.fujitsu.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

1 files changed, 7 insertions, 1 deletions

diff --git a/include/net/sctp/structs.h b/include/net/sctp/structs.h
index 917d425f0542..67592072a32e 100644
--- a/include/net/sctp/structs.h
+++ b/include/net/sctp/structs.h
@@ -902,7 +902,10 @@ struct sctp_transport {
          *              calculation completes (i.e. the DATA chunk
          *              is SACK'd) clear this flag.
          */
-        int rto_pending;
+        __u8 rto_pending;
+
+        /* Flag to track the current fast recovery state */
+        __u8 fast_recovery;
 
         /*
          * These are the congestion stats.
@@ -921,6 +924,9 @@ struct sctp_transport {
         /* Data that has been sent, but not acknowledged. */
         __u32 flight_size;
 
+        /* TSN marking the fast recovery exit point */
+        __u32 fast_recovery_exit;
+
         /* Destination */
         struct dst_entry *dst;
         /* Source address. */