[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1k4vl9yct.fsf@fess.ebiederm.org>
Date: Wed, 13 Jan 2010 19:09:06 -0800
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Miles Lane <miles.lane@...il.com>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Américo Wang <xiyou.wangcong@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
Arjan van de Ven <arjan@...radead.org>,
Tejun Heo <tj@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: 2.6.33-rc3 -- INFO: possible recursive locking -- (s_active){++++.+}, at: [<c10d2941>] sysfs_hash_and_remove+0x3d/0x4f
Miles Lane <miles.lane@...il.com> writes:
> Hmm. I tried your patch applied to a clean 2.6.33-rc4 tree, and used
> the same .config file. This time the INFO looks a lot like my
> original bug report. Weird. Maybe I am doing something wrong!
I agree weird. Either you don't have my patch working correctly or I
talk a good good game but I don't have a clue about lockdep
subclasses.
Grrr.
Now to see if I can find some time to dig into this. Thank you very
much for testing.
Eric
--
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/
Powered by blists - more mailing lists