diff options
| author | Tung Nguyen <[email protected]> | 2023-01-05 06:02:51 +0000 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2023-01-06 12:53:10 +0000 |
| commit | c244c092f1ed2acfb5af3d3da81e22367d3dd733 (patch) | |
| tree | 66b0953420eff8cd9656132c25ece576ef3c3cd6 /tools/testing/selftests/bpf/prog_tests/autoload.c | |
| parent | eea8ce81fbb544e3caad1a1c876ba1af467b3d3c (diff) | |
tipc: fix unexpected link reset due to discovery messages
This unexpected behavior is observed:
node 1 | node 2
------ | ------
link is established | link is established
reboot | link is reset
up | send discovery message
receive discovery message |
link is established | link is established
send discovery message |
| receive discovery message
| link is reset (unexpected)
| send reset message
link is reset |
It is due to delayed re-discovery as described in function
tipc_node_check_dest(): "this link endpoint has already reset
and re-established contact with the peer, before receiving a
discovery message from that node."
However, commit 598411d70f85 has changed the condition for calling
tipc_node_link_down() which was the acceptance of new media address.
This commit fixes this by restoring the old and correct behavior.
Fixes: 598411d70f85 ("tipc: make resetting of links non-atomic")
Acked-by: Jon Maloy <[email protected]>
Signed-off-by: Tung Nguyen <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions