netdev - Re: [PATCH net] packet: call fanout_release, while UNREGISTERING a netdev

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 2 Feb 2017 16:44:13 +0000
From:   Anoob Soman <anoob.soman@...rix.com>
To:     Eric Dumazet <eric.dumazet@...il.com>
CC:     David Miller <davem@...emloft.net>, <netdev@...r.kernel.org>
Subject: Re: [PATCH net] packet: call fanout_release, while UNREGISTERING a
 netdev

On 02/02/17 15:53, Eric Dumazet wrote:
> On Thu, 2017-02-02 at 14:42 +0000, Anoob Soman wrote:
>
>> I have tested both the approaches and LOCKDEP doesn't seem to catch any
>> problem with the test I was doing.
> Yeah, I think I will cleanup this mess, we probably can remove rcu
> locking in control path, and stick to a single mutex to reduce all this
> lock complexity.
>
> But that will be for net-next, while we need your fix for net tree.
>
> Thanks.
>
>
Sorry, I didn't get it. You want me to post a patch for net tree, 
changing the way we do dev_{add,remove}_pack(fanout_prot_hook) and you 
will fix up the lock mess in net-next.

Thanks,
Anoob.