From: Andrew Morton <akpm@linux-foundation.org>
To: "Miles Lane" <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Nishanth Aravamudan <nacc@us.ibm.com>,
Adam Litke <agl@us.ibm.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: 2.6.24-git20 -- BUG: sleeping function called from invalid context at include/asm/uaccess_32.h:449
Date: Sat, 9 Feb 2008 16:26:43 -0800 [thread overview]
Message-ID: <20080209162643.fd3822f1.akpm@linux-foundation.org> (raw)
In-Reply-To: <a44ae5cd0802091103s4c24c70fyc747d9c4ab9a9897@mail.gmail.com>
On Sat, 9 Feb 2008 14:03:28 -0500 "Miles Lane" <miles.lane@gmail.com> wrote:
> Command run:
> find /proc | xargs tail
>
> [ 2710.028219] BUG: sleeping function called from invalid context at
> include/asm/uaccess_32.h:449
> [ 2710.028229] in_atomic():1, irqs_disabled():0
> [ 2710.028232] 1 lock held by head/9380:
> [ 2710.028234] #0: (hugetlb_lock){--..}, at: [<c016734f>]
> hugetlb_overcommit_handler+0x16/0x3e
> [ 2710.028248] Pid: 9380, comm: head Not tainted 2.6.24-git20 #5
> [ 2710.028260] [<c0118749>] __might_sleep+0xc2/0xc9
> [ 2710.028267] [<c021cb39>] copy_to_user+0x32/0x49
> [ 2710.028277] [<c0123f6a>] do_proc_doulongvec_minmax+0x1df/0x27f
> [ 2710.028289] [<c012403c>] proc_doulongvec_minmax+0x15/0x17
> [ 2710.028295] [<c0167363>] hugetlb_overcommit_handler+0x2a/0x3e
> [ 2710.028303] [<c01a1462>] proc_sys_read+0x5e/0x7b
> [ 2710.028311] [<c01a1404>] ? proc_sys_read+0x0/0x7b
> [ 2710.028317] [<c0170d7a>] vfs_read+0x8a/0x106
> [ 2710.028325] [<c017116f>] sys_read+0x3b/0x60
> [ 2710.028331] [<c0103e32>] sysenter_past_esp+0x5f/0xa5
Ugh, how did I let that one through?
Guys, how often mut it be said? PLEASE always test all code with all
kernel deubg options enabled.
next prev parent reply other threads:[~2008-02-10 0:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 19:03 2.6.24-git20 -- BUG: sleeping function called from invalid context at include/asm/uaccess_32.h:449 Miles Lane
2008-02-10 0:26 ` Andrew Morton [this message]
2008-02-10 0:38 ` Arjan van de Ven
2008-02-10 10:44 ` Stefan Richter
2008-02-10 21:26 ` Nishanth Aravamudan
2008-02-10 21:25 ` Nishanth Aravamudan
2008-02-11 22:28 ` Nishanth Aravamudan
2008-02-12 3:57 ` Miles Lane
2008-02-12 4:17 ` Miles Lane
2008-02-12 5:16 ` Nishanth Aravamudan
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=20080209162643.fd3822f1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=agl@us.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=nacc@us.ibm.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