lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 8 Jul 2019 10:18:46 +0200 From: Eric Dumazet <eric.dumazet@...il.com> To: Chris Packham <chris.packham@...iedtelesis.co.nz>, jon.maloy@...csson.com, ying.xue@...driver.com, davem@...emloft.net Cc: netdev@...r.kernel.org, tipc-discussion@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: [PATCH] tipc: ensure skb->lock is initialised On 7/8/19 12:53 AM, Chris Packham wrote: > 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. > Ensure tipc_named_node_up() uses skb_queue_head_init() so that the lock > is explicitly initialised. > > Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz> I would rather change the faulty skb_queue_purge() to __skb_queue_purge()
Powered by blists - more mailing lists