sctp: teach CACC algorithm about removed transports
authorVlad Yasevich <vladislav.yasevich@hp.com>
Mon, 18 Apr 2011 19:13:56 +0000 (19:13 +0000)
committerDavid S. Miller <davem@davemloft.net>
Wed, 20 Apr 2011 04:45:21 +0000 (21:45 -0700)
commitf246a7b7c5b9df0ea0f0807a7101995af5e83213
tree4362f120c0f483b603407f04c66a0f7b472b0287
parent934253a7b4ab4151037ea9532552628723a14442
sctp: teach CACC algorithm about removed transports

When we have have to remove a transport due to ASCONF, we move
the data to a new active path.  This can trigger CACC algorithm
to not mark that data as missing when SACKs arrive.  This is
because the transport passed to the CACC algorithm is the one
this data is sitting on, not the one it was sent on (that one
may be gone).  So, by sending the original transport (even if
it's NULL), we may start marking data as missing.

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