From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: David Rientjes <rientjes@google.com>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Sasha Levin <levinsasha928@gmail.com>
Subject: Re: BUG: sleeping function called from invalid context at fs/proc/task_mmu.c:826
Date: Thu, 29 Mar 2012 04:48:57 -0400 [thread overview]
Message-ID: <4F7421F9.8010907@ah.jp.nec.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1203281706430.8554@chino.kir.corp.google.com>
(3/28/2012 20:09), David Rientjes wrote:
> On Wed, 28 Mar 2012, Dave Jones wrote:
>
>> Just hit this on v3.3-7919-g6658a69
>>
>> Dave
>>
>> BUG: sleeping function called from invalid context at fs/proc/task_mmu.c:826
>> in_atomic(): 1, irqs_disabled(): 0, pid: 15123, name: trinity
>> INFO: lockdep is turned off.
>> Pid: 15123, comm: trinity Not tainted 3.3.0+ #30
>> Call Trace:
>> [<ffffffff8109bf75>] __might_sleep+0x145/0x200
>> [<ffffffff8122ee77>] ? pagemap_pte_range+0x67/0x340
>> [<ffffffff8122ef3f>] pagemap_pte_range+0x12f/0x340
>> [<ffffffff811924b9>] walk_page_range+0x389/0x520
>> [<ffffffff8122e9a2>] pagemap_read+0x282/0x350
>> [<ffffffff8122ee10>] ? clear_refs_pte_range+0x180/0x180
>> [<ffffffff8122d340>] ? get_vmalloc_info+0x110/0x110
>> [<ffffffff8122e5c0>] ? pid_numa_maps_open+0x20/0x20
>> [<ffffffff811c3a43>] vfs_read+0xb3/0x180
>> [<ffffffff811c3b5d>] sys_read+0x4d/0x90
>> [<ffffffff816c02a9>] system_call_fastpath+0x16/0x1b
>>
>
> This looks like it was already reported as
> http://marc.info/?l=linux-kernel&m=133289254323384 by Sasha Levin. We're
> waiting for a patch to push to stable from Naoya Horiguchi.
I posted a fix patch.
Please see http://marc.info/?l=linux-mm&m=133301049801146&w=2
Thanks,
Naoya
prev parent reply other threads:[~2012-03-29 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 18:18 BUG: sleeping function called from invalid context at fs/proc/task_mmu.c:826 Dave Jones
2012-03-29 0:09 ` David Rientjes
2012-03-29 8:48 ` Naoya Horiguchi [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=4F7421F9.8010907@ah.jp.nec.com \
--to=n-horiguchi@ah.jp.nec.com \
--cc=davej@redhat.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.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