Re: [patch net-next v2 2/2] net: introduce netif_addr_lock_nested() and call if when appropriate

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Mon, Jan 09, 2012 at 08:07:08PM CET, bhutchings@xxxxxxxxxxxxxx wrote:
>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'?

That's him :) I mixed that up a bit. Sorry :(

Jirka

>
>Ben.
>
>-- 
>Ben Hutchings, Staff Engineer, Solarflare
>Not speaking for my employer; that's the marketing department's job.
>They asked us to note that Solarflare product names are trademarked.
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Linux Kernel Discussion]     [Ethernet Bridging]     [Linux Wireless Networking]     [Linux Bluetooth Networking]     [Linux Networking Users]     [VLAN]     [Git]     [IETF Annouce]     [Linux Assembly]     [Security]     [Bugtraq]     [Photo]     [Singles Social Networking]     [Yosemite Information]     [MIPS Linux]     [ARM Linux Kernel]     [ARM Linux]     [Linux Virtualization]     [Linux Security]     [Linux IDE]     [Linux RAID]     [Linux SCSI]     [Free Dating]

Add to Google Powered by Linux