linux-kernel - Re: [BUG]: Possibe recursive locking detected in sysfs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <520f0cf11002141822i7c77c58cl2e00305ca6890f90@mail.gmail.com>
Date:	Sun, 14 Feb 2010 21:22:06 -0500
From:	John Kacur <jkacur@...hat.com>
To:	Eric Biederman <ebiederm@...stanetworks.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...e.de>, Tejun Heo <tj@...nel.org>,
	Serge Hallyn <serue@...ibm.com>,
	"David P. Quigley" <dpquigl@...ho.nsa.gov>,
	James Morris <jmorris@...ei.org>
Subject: Re: [BUG]: Possibe recursive locking detected in sysfs

On Sun, Feb 14, 2010 at 4:50 PM, Eric Biederman
<ebiederm@...stanetworks.com> wrote:
>> Sure, are you referring to the patch-set that begins with
>> "[PATCH 1/6] sysfs: Serialize updates to the vfs inode"?
>
> Sorry no.
>
> http://lkml.org/lkml/2010/2/11/329
>

I applied your patch, and yes, it removed the possible recursive
locking detected message, but everything still froze.
I don't think I really have any good info from the crash to report.
Your patch seems to have added the symptom of a huge number of
BUG: key ffff880126269e40 not in .data!
BUG: key ffff880136fc03f0 not in .data!

messages to my log.

If there is any other info that I can provide that would be useful,
please let me know.
--
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/