From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Minchan Kim <minchan.kim@gmail.com>, Len Brown <lenb@kernel.org>,
inux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg KH <greg@kroah.com>
Subject: Re: [BUG?] recursive locking in acpi_bus_register_driver
Date: Tue, 9 Feb 2010 10:13:21 +0800 [thread overview]
Message-ID: <2375c9f91002081813w32a59b29l42c734cb2271324c@mail.gmail.com> (raw)
In-Reply-To: <20100208124845.f652e951.akpm@linux-foundation.org>
On Tue, Feb 9, 2010 at 4:48 AM, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 5 Feb 2010 15:58:07 +0900
> Minchan Kim <minchan.kim@gmail.com> wrote:
>
>> Is this a known bug or my hardware is bad ?
>> I use mmotm 2010-02-03-20-09.
>>
>> I didn't have a problem in 2.6.32.
>> Unfortunately I can't test it at next week.
>> I hope this problem can be reproduced easily.
>>
>
> It would be useful if you could work out whether this bug is only in
> -mm, or is in linux-next or is in mainline, please.
>
> Probably it's in linux-next, and it might be due to driver core changes
> or acpi changes.
>
Due the convert from semphore to mutex in driver core code, I think.
This is a known issue.
> Either way, we should get this weeded out lest the offending code turns
> up in 2.6.34-rc1.
Alan Stern is working on this, the patch he provided still needs to be
discussed, I think.
prev parent reply other threads:[~2010-02-09 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 6:58 [BUG?] recursive locking in acpi_bus_register_driver Minchan Kim
2010-02-08 20:48 ` Andrew Morton
2010-02-09 2:13 ` Américo Wang [this message]
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=2375c9f91002081813w32a59b29l42c734cb2271324c@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=inux-acpi@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan.kim@gmail.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).