netdev - Re: [patch net-next v2 2/2] net: introduce netif_addr_lock

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]

Message-Id: <20120109.124723.2024034017916493404.davem@davemloft.net>
Date:	Mon, 09 Jan 2012 12:47:23 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	bhutchings@...arflare.com
Cc:	jpirko@...hat.com, netdev@...r.kernel.org, eric.dumazet@...il.com
Subject: Re: [patch net-next v2 2/2] net: introduce
 netif_addr_lock_nested() and call if when appropriate

From: Ben Hutchings <bhutchings@...arflare.com>
Date: Mon, 9 Jan 2012 19:07:08 +0000

> On Mon, 2012-01-09 at 17:36 +0100, Jiri Pirko wrote:
>> dev_uc_sync() and dev_mc_sync() are acquiring netif_addr_lock for
>> destination device of synchronization. Since netif_addr_lock is already
>> held at the time for source device, this triggers depmod deathlock
>> warning.
> [...]
> 
> I think you mean '...lockdep deadlock warning'?

Applied with this wording fixed.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html