From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: John Kacur <jkacur@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG]: Possibe recursive locking detected in sysfs
Date: Mon, 15 Feb 2010 20:41:18 +0100 [thread overview]
Message-ID: <201002152041.18800.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <520f0cf11002110911t3f125649v73062e9851e2cfb3@mail.gmail.com>
On czwartek, 11 lutego 2010 o 18:11:46 John Kacur wrote:
> I'm not sure if this one has already been reported. - thanks.
>
> Feb 11 07:24:15 localhost kernel: [ INFO: possible recursive locking
> detected ] Feb 11 07:24:15 localhost kernel: 2.6.33-rc7 #1
[...]
I created a Bugzilla entry at http://bugzilla.kernel.org/show_bug.cgi?id=15319
for your bug report, please add your address to the CC list in there, thanks!
--
Maciej Rutecki
http://www.maciek.unixy.pl
prev parent reply other threads:[~2010-02-15 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 17:11 [BUG]: Possibe recursive locking detected in sysfs John Kacur
2010-02-14 13:10 ` John Kacur
2010-02-14 14:57 ` Eric Biederman
2010-02-14 20:54 ` John Kacur
2010-02-14 21:50 ` Eric Biederman
2010-02-15 2:22 ` John Kacur
2010-02-15 9:56 ` Eric Biederman
2010-02-15 10:33 ` Américo Wang
2010-02-15 19:41 ` Maciej Rutecki [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=201002152041.18800.maciej.rutecki@gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.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