netdev - Re: iw lockdep warning on wireless-testing

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] [day] [month] [year] [list]

Date:	Tue, 24 Jun 2008 17:03:19 +0200
From:	Jarek Poplawski <jarkao2@...il.com>
To:	Zhu Yi <public-yi.zhu-ral2JQCrhuEAvxtiuMwx3w@...h.gmane.org>
CC:	Johannes Berg 
	<public-johannes-cdvu00un1VgdHxzADdlk8Q@...h.gmane.org>,
	public-linux-wireless-u79uwXL29TY76Z2rM5mHXA@...h.gmane.org,
	Thomas Graf <public-tgraf-G/eBtMaohhA@...h.gmane.org>,
	netdev <public-netdev-u79uwXL29TY76Z2rM5mHXA@...h.gmane.org>
Subject: Re: iw lockdep warning on wireless-testing




Zhu Yi wrote, On 06/24/2008 11:05 AM:

> On Tue, 2008-06-24 at 10:59 +0200, Johannes Berg wrote:
>>> [ INFO: possible circular locking dependency detected ]
>>> 2.6.26-rc6-wl #57
>>> -------------------------------------------------------
>>> iw/2763 is trying to acquire lock:
>>>  (genl_mutex){--..}, at: [<ffffffff81216e4c>] ctrl_dumpfamily
>> +0x31/0xf7
>>> but task is already holding lock:
>>>  (nlk->cb_mutex){--..}, at: [<ffffffff812137c8>] netlink_dump
>> +0x40/0x19d
>>> which lock already depends on the new lock.
>> None of those is anything nl80211 has influence over, afaict.
> 
> Agreed. I can follow the two scenarios below. Apparently it's a ABBA
> locking issue. Just don't know which should be the correct sequence for
> using with the two locks.
> 

It should be fixed by this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=6d1a3fb567a728d31474636e167c324702a0c38b

Regards,
Jarek P.


--
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