diff options
| author | Jon Maloy <jmaloy@redhat.com> | 2022-02-13 20:38:52 -0500 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2022-02-14 21:18:18 -0800 |
| commit | 032062f363b4bf02b1d547f329aa5d97b6a17410 (patch) | |
| tree | db657eb5821c4de80deca3f539ede4caa428280b /net/tipc | |
| parent | 6605cc67ca18b9d583eb96e18a20f5f4e726103c (diff) | |
| download | linux-032062f363b4bf02b1d547f329aa5d97b6a17410.tar.gz linux-032062f363b4bf02b1d547f329aa5d97b6a17410.tar.bz2 linux-032062f363b4bf02b1d547f329aa5d97b6a17410.zip | |
tipc: fix wrong publisher node address in link publications
When a link comes up we add its presence to the name table to make it
possible for users to subscribe for link up/down events. However, after
a previous call signature change the binding is wrongly published with
the peer node as publishing node, instead of the own node as it should
be. This has the effect that the command 'tipc name table show' will
list the link binding (service type 2) with node scope and a peer node
as originator, something that obviously is impossible.
We correct this bug here.
Fixes: 50a3499ab853 ("tipc: simplify signature of tipc_namtbl_publish()")
Signed-off-by: Jon Maloy <jmaloy@redhat.com>
Link: https://lore.kernel.org/r/20220214013852.2803940-1-jmaloy@redhat.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/tipc')
| -rw-r--r-- | net/tipc/node.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/net/tipc/node.c b/net/tipc/node.c index 9947b7dfe1d2..fd95df338da7 100644 --- a/net/tipc/node.c +++ b/net/tipc/node.c @@ -413,7 +413,7 @@ static void tipc_node_write_unlock(struct tipc_node *n) tipc_uaddr(&ua, TIPC_SERVICE_RANGE, TIPC_NODE_SCOPE, TIPC_LINK_STATE, n->addr, n->addr); sk.ref = n->link_id; - sk.node = n->addr; + sk.node = tipc_own_addr(net); bearer_id = n->link_id & 0xffff; publ_list = &n->publ_list; |