From: "Américo Wang" <xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
Cc: Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Maciej Rutecki
<maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Eric Biederman
<ebiederm-BGArkANP9klv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>,
John Kacur <jkacur-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [Bug #15319] [BUG]: Possibe recursive locking detected in sysfs
Date: Mon, 22 Feb 2010 09:31:34 +0800 [thread overview]
Message-ID: <2375c9f91002211731y354a7975oc863db321375d330@mail.gmail.com> (raw)
In-Reply-To: <ClJsQB_ZlxO.A.S_E.RcagLB@chimera>
On Mon, Feb 22, 2010 at 5:30 AM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.32. Please verify if it still should be listed and let the tracking team
> know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15319
> Subject : [BUG]: Possibe recursive locking detected in sysfs
> Submitter : John Kacur <jkacur-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> Date : 2010-02-11 17:11 (11 days old)
> Message-ID : <520f0cf11002110911t3f125649v73062e9851e2cfb3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
> References : http://marc.info/?l=linux-kernel&m=126590832432598&w=2
> Handled-By : Eric Biederman <ebiederm@aristanetworks.com>
>
>
http://lkml.org/lkml/2010/2/11/329
next prev parent reply other threads:[~2010-02-22 1:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b_eAfX__uZL.A.lvE.HcagLB@chimera>
[not found] ` <ClJsQB_ZlxO.A.wdH.7fagLB@chimera>
2010-02-21 23:37 ` [Bug #15039] leds_alix2: can't allocate I/O for GPIO Daniel Mack
[not found] ` <ClJsQB_ZlxO.A.eNH.WeagLB@chimera>
2010-02-22 1:25 ` [Bug #15142] sysfs-related lockdep warning in __blkdev_get Américo Wang
[not found] ` <ClJsQB_ZlxO.A.YyG.4dagLB@chimera>
2010-02-22 1:30 ` [Bug #15202] lockdep warning during elevator_switch Américo Wang
[not found] ` <2375c9f91002211730l6835cae1x1693da3d94fccc0c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-25 1:03 ` Hugh Dickins
[not found] ` <alpine.LSU.2.00.1002250051380.4394-T/S/X05ZC3jbmfIwyoSfiQ@public.gmane.org>
2010-02-25 1:35 ` Eric W. Biederman
[not found] ` <ClJsQB_ZlxO.A.S_E.RcagLB@chimera>
2010-02-22 1:31 ` Américo Wang [this message]
2010-03-21 20:27 2.6.34-rc2: Reported regressions 2.6.32 -> 2.6.33 Rafael J. Wysocki
2010-03-21 20:30 ` [Bug #15319] [BUG]: Possibe recursive locking detected in sysfs Rafael J. Wysocki
2010-03-26 3:59 ` Eric W. Biederman
[not found] ` <m1vdcjohr1.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2010-03-26 21:58 ` Rafael J. Wysocki
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=2375c9f91002211731y354a7975oc863db321375d330@mail.gmail.com \
--to=xiyou.wangcong-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ebiederm-BGArkANP9klv6pq1l3V1OdBPR1lH4CV8@public.gmane.org \
--cc=jkacur-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=rjw-KKrjLPT3xs0@public.gmane.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).