tipc: update mon's self addr when node addr generated
In commit25b0b9c4e8
("tipc: handle collisions of 32-bit node address hash values"), the 32-bit node address only generated after one second trial period expired. However the self's addr in struct tipc_monitor do not update according to node address generated. This lead to it is always zero as initial value. As result, sorting algorithm using this value does not work as expected, neither neighbor monitoring framework. In this commit, we add a fix to update self's addr when 32-bit node address generated. Fixes:25b0b9c4e8
("tipc: handle collisions of 32-bit node address hash values") Acked-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: Hoang Le <hoang.h.le@dektech.com.au> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:

committed by
David S. Miller

parent
0320d1e7a3
commit
46cb01eeeb
@@ -77,6 +77,7 @@ int __tipc_nl_add_monitor(struct net *net, struct tipc_nl_msg *msg,
|
||||
u32 bearer_id);
|
||||
int tipc_nl_add_monitor_peer(struct net *net, struct tipc_nl_msg *msg,
|
||||
u32 bearer_id, u32 *prev_node);
|
||||
void tipc_mon_reinit_self(struct net *net);
|
||||
|
||||
extern const int tipc_max_domain_size;
|
||||
#endif
|
||||
|
Reference in New Issue
Block a user