tipc: ensure head->lock is initialised
tipc_named_node_up() creates a skb list. It passes the list to tipc_node_xmit() which has some code paths that can call skb_queue_purge() which relies on the list->lock being initialised. The spin_lock is only needed if the messages end up on the receive path but when the list is created in tipc_named_node_up() we don't necessarily know if it is going to end up there. Once all the skb list users are updated in tipc it will then be possible to update them to use the unlocked variants of the skb list functions and initialise the lock when we know the message will follow the receive path. Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz> Acked-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
100c4043b8
commit
d12cffe932
@ -190,7 +190,7 @@ void tipc_named_node_up(struct net *net, u32 dnode)
|
||||
struct name_table *nt = tipc_name_table(net);
|
||||
struct sk_buff_head head;
|
||||
|
||||
__skb_queue_head_init(&head);
|
||||
skb_queue_head_init(&head);
|
||||
|
||||
read_lock_bh(&nt->cluster_scope_lock);
|
||||
named_distribute(net, &head, dnode, &nt->cluster_scope);
|
||||
|
Loading…
Reference in New Issue
Block a user