From: "Paul Menage" <menage@google.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Miles Lane" <miles.lane@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Dag Brattli" <dagb@cs.uit.no>,
samuel@sortiz.org
Subject: Re: 2.6.23-rc1-mm1 -- INFO: possible recursive locking detected -- (&hashbin->hb_spinlock){....}, at: [<c03d95d3>] irias_seq_show+0xba/0x1a8
Date: Sun, 29 Jul 2007 22:44:07 -0700 [thread overview]
Message-ID: <6599ad830707292244x3dbdf662l95de9bf3c1f5614e@mail.gmail.com> (raw)
In-Reply-To: <20070728013859.5125f685.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On 7/28/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> > [<c0154ad2>] proc_cpuset_show+0x5e/0xb9
> > [<c01976b1>] seq_read+0xef/0x266
> > [<c0181398>] vfs_read+0x8e/0x117
> > [<c01817c9>] sys_read+0x3d/0x61
> > [<c010401e>] sysenter_past_esp+0x5f/0x99
> > =======================
> > INFO: lockdep is turned off.
> > Code: 00 89 d8 83 c4 0c 5b 5e 5f 5d c3 55 89 e5 57 56 53 83 ec 08 89
> > 45 f0 89 55 ec 89 d3 01 cb 8d 43 ff c6 43 ff 00 8b 55 f0 8b 72 1c <8b>
> > 56 3c 29 d0 3b 45 ec 72 45 89 d1 c1 e9 02 8b 76 40 89 c7 f3
> > EIP: [<c01536a7>] container_path+0x20/0x7b SS:ESP 0068:c5ccff00
>
Oops, this is a case of trying to read /proc/self/cpuset when cpusets
are completely unmounted. It works fine when cpusets is mounted as
part of any hierarchy, or part of an active but unmounted hierarchy.
Attached patch fixes it, and should be rolled in to the first patch of
the series. (basic framework patch).
Paul
[-- Attachment #2: fix-proc-self-cpuset.patch --]
[-- Type: text/x-patch, Size: 573 bytes --]
---
kernel/container.c | 9 +++++++++
1 file changed, 9 insertions(+)
Index: container-2.6.22-rc6-mm1/kernel/container.c
===================================================================
--- container-2.6.22-rc6-mm1.orig/kernel/container.c
+++ container-2.6.22-rc6-mm1/kernel/container.c
@@ -684,6 +684,15 @@ int container_path(const struct containe
{
char *start;
+ if (cont == dummytop) {
+ /*
+ * Inactive subsystems have no dentry for their root
+ * container
+ */
+ strcpy(buf, "/");
+ return 0;
+ }
+
start = buf + buflen;
*--start = '\0';
prev parent reply other threads:[~2007-07-30 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 7:01 Miles Lane
2007-07-28 8:38 ` Andrew Morton
2007-07-30 5:44 ` Paul Menage [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=6599ad830707292244x3dbdf662l95de9bf3c1f5614e@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=dagb@cs.uit.no \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=samuel@sortiz.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
all inboxes | Powered by JetHome®