lkml.org 
[lkml]   [2010]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: 2.6.33.3: possible recursive locking detected
From
On Wed, May 5, 2010 at 10:32 AM, Yong Zhang <yong.zhang@windriver.com> wrote:
> On Tue, May 04, 2010 at 11:37:37AM +0300, Avi Kivity wrote:
>> On 05/04/2010 10:03 AM, CaT wrote:
>> >I'm currently running 2.6.33.3 in a KVM instance emulating a core2duo
>> >on 1 cpu with virtio HDs running on top of a core2duo host running 2.6.33.3.
>> >qemu-kvm version 0.12.3.
>
> Can you try commit 6992f5334995af474c2b58d010d08bc597f0f2fe in the latest
> kernel?
>

Hmm, 2.6.33 -stable has commit 846f99749ab68bbc7f75c74fec305de675b1a1bf?

Actually, these 3 commits fixed it:

6992f5334995af474c2b58d010d08bc597f0f2fe sysfs: Use one lockdep class
per sysfs ttribute.
a2db6842873c8e5a70652f278d469128cb52db70 sysfs: Only take active
references on attributes.
e72ceb8ccac5f770b3e696e09bb673dca7024b20 sysfs: Remove sysfs_get/put_active_two

However, there are many other patches needed to amend these, so I think
it's not suitable for -stable to include, perhaps a revert of
846f99749ab68bbc7f75c74fec305de675b1a1bf is better.

Adding Greg into Cc.

Thanks.


\
 
 \ /
  Last update: 2010-05-05 05:01    [W:0.065 / U:88.944 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site