linux-kernel - Re: 2.6.20-rc2-mm1 -- INFO: possible recursive locking detected

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: <20070104214747.GD28445@suse.de>
Date:	Thu, 4 Jan 2007 13:47:47 -0800
From:	Greg KH <gregkh@...e.de>
To:	Miles Lane <miles.lane@...il.com>
Cc:	Andrew Morton <akpm@...l.org>, LKML <linux-kernel@...r.kernel.org>,
	yi.zhu@...el.com
Subject: Re: 2.6.20-rc2-mm1 -- INFO: possible recursive locking detected

On Sat, Dec 30, 2006 at 02:47:20AM -0800, Miles Lane wrote:
> Sorry Andrew, I am not sure which maintainer to contact about this.  I
> CCed gregkh for sysfs and Yi for ipw2200.  Hopefully this is helpful.
> BTW, I also found that none of my network drivers were recognized by
> hal (lshal did not show their "net" entries) unless I set
> CONFIG_SYSFS_DEPRECATED=y.  I am running Ubuntu development (Feisty
> Fawn), so it seems like I ought to be running pretty current hal
> utilities:   hal-device-manager       0.5.8.1-4ubuntu1.  After
> reenabling CONFIG_SYSFS_DEPRECATED, I am able to use my IPW2200
> driver, in spite of this recursive locking message, so this INFO
> message may not indicate a problem.

Does this show up on the 2.6.20-rc3 kernel too?

thanks,

greg k-h
-
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/