diff options
| author | Chang Xiangzhong <changxiangzhong@gmail.com> | 2013-11-14 03:58:26 +0400 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2013-11-15 01:35:09 +0400 |
| commit | d30a58ba2ef5092f10985d357d22acab232b6dcc (patch) | |
| tree | d77f00f64662b1c41bceda5083c123b55650e11e /REPORTING-BUGS | |
| parent | dccf76ca6b626c0c4a4e09bb221adee3270ab0ef (diff) | |
| download | linux-d30a58ba2ef5092f10985d357d22acab232b6dcc.tar.xz | |
net: sctp: bug-fixing: retran_path not set properly after transports recovering (v3)
When a transport recovers due to the new coming sack, SCTP should
iterate all of its transport_list to locate the __two__ most recently used
transport and set to active_path and retran_path respectively. The exising
code does not find the two properly - In case of the following list:
[most-recent] -> [2nd-most-recent] -> ...
Both active_path and retran_path would be set to the 1st element.
The bug happens when:
1) multi-homing
2) failure/partial_failure transport recovers
Both active_path and retran_path would be set to the same most-recent one, in
other words, retran_path would not take its role - an end user might not even
notice this issue.
Signed-off-by: Chang Xiangzhong <changxiangzhong@gmail.com>
Acked-by: Vlad Yasevich <vyasevich@gmail.com>
Acked-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'REPORTING-BUGS')
0 files changed, 0 insertions, 0 deletions