linux-kernel - Re: 26-rc9-mmotm lockdep warning initializing loopback interface

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]

Message-ID: <20080714060933.GA4034@ff.dom.local>
Date:	Mon, 14 Jul 2008 06:09:33 +0000
From:	Jarek Poplawski <jarkao2@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Valdis.Kletnieks@...edu, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
	Alexander Beregalov <a.beregalov@...il.com>
Subject: Re: 26-rc9-mmotm lockdep warning initializing loopback interface

On 14-07-2008 06:07, Andrew Morton wrote:
> On Sun, 13 Jul 2008 06:00:03 -0400 Valdis.Kletnieks@...edu wrote:
...
>> Found this in the dmesg:
>>
>> [    0.418581] system 00:0b: iomem range 0xfed00000-0xfed003ff has been reserved
>> [    0.421109]
>> [    0.421110] =============================================
>> [    0.421123] [ INFO: possible recursive locking detected ]
>> [    0.421132] 2.6.26-rc9-mm1 #2
>> [    0.421138] ---------------------------------------------
>> [    0.421147] swapper/1 is trying to acquire lock:
>> [    0.421154]  (&queue->lock){-...}, at: [<ffffffff804b81d5>] qdisc_lock_tree+0x27/0x2c
>> [    0.421176]
>> [    0.421177] but task is already holding lock:
>> [    0.421186]  (&queue->lock){-...}, at: [<ffffffff804b81cd>] qdisc_lock_tree+0x1f/0x2c
...
> (otoh, many of these problems are also in linux-next.  Who's testing
> that?  Hopefully it's a weekend*summer thing.)

http://permalink.gmane.org/gmane.linux.kernel.next/1514

Jarek P.

PS: it's only about lockdep annotation, and could be fixed with
other way finally.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/