sctp: allow increasing cwnd regardless of ctsn moving or not
authorMarcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Fri, 23 Jun 2017 22:59:34 +0000 (19:59 -0300)
committerDavid S. Miller <davem@davemloft.net>
Sun, 25 Jun 2017 18:43:53 +0000 (14:43 -0400)
commite56f777af82ebbdf8302164b040128d890f100d8
tree93b0efe040642e8b76bb1642a71f93c4e68aa4eb
parentd0b53f40977446fdf2460b14d4544d1375a3138d
sctp: allow increasing cwnd regardless of ctsn moving or not

As per RFC4960 Errata 3.22, this condition is not needed anymore as it
could cause the partial_bytes_acked to not consider the TSNs acked in
the Gap Ack Blocks although they were received by the peer successfully.

This patch thus drops the check for new Cumulative TSN Ack Point,
leaving just the flight_size < cwnd one.

See-also: https://tools.ietf.org/html/draft-ietf-tsvwg-rfc4960-errata-01#section-3.22
Signed-off-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/sctp/transport.c