From: CaT <cat@zip.com.au>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Yong Zhang <yong.zhang@windriver.com>,
lkml@zip.com.au, mtosatti@redhat.com, kvm@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Avi Kivity <avi@redhat.com>, Greg KH <gregkh@suse.de>
Subject: Re: 2.6.33.3: possible recursive locking detected
Date: Tue, 11 May 2010 21:33:50 +1000 [thread overview]
Message-ID: <20100511113350.GW2657@zip.com.au> (raw)
In-Reply-To: <h2p2375c9f91005041952k422e7701vf7e726fc5440e953@mail.gmail.com>
On Wed, May 05, 2010 at 10:52:50AM +0800, Américo Wang wrote:
> 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.
Slightly at a loss as to what to do, now. It's a virt instance so I can
apply patches at will but, well, clarity is good. :)
--
"A search of his car uncovered pornography, a homemade sex aid, women's
stockings and a Jack Russell terrier."
- http://www.news.com.au/story/0%2C27574%2C24675808-421%2C00.html
next prev parent reply other threads:[~2010-05-11 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 7:03 2.6.33.3: possible recursive locking detected CaT
2010-05-04 8:37 ` Avi Kivity
2010-05-05 2:32 ` Yong Zhang
2010-05-05 2:52 ` Américo Wang
2010-05-11 11:33 ` CaT [this message]
2010-05-11 15:03 ` Greg KH
2010-05-12 4:34 ` Américo Wang
2010-05-12 19:46 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100511113350.GW2657@zip.com.au \
--to=cat@zip.com.au \
--cc=avi@redhat.com \
--cc=gregkh@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@zip.com.au \
--cc=mtosatti@redhat.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yong.zhang@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).