From: Giridhar Pemmasani <giri@lmc.cs.sunysb.edu>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
Date: Mon, 22 May 2006 02:01:33 -0400 [thread overview]
Message-ID: <20060522060133.91683EE9EE@wolfe.lmc.cs.sunysb.edu> (raw)
In-Reply-To: <1148262697.3902.55.camel@laptopd505.fenrus.org>
On Mon, 22 May 2006 03:51:37 +0200, Arjan van de Ven <arjan@infradead.org> said:
> On Sun, 2006-05-21 at 21:36 -0400, Giridhar Pemmasani wrote:
>> If __vmalloc is called in atomic context with GFP_ATOMIC flags,
>> __get_vm_area_node is called, which calls kmalloc_node with
>> GFP_KERNEL flags. This causes 'sleeping function called from
>> invalid context at mm/slab.c:2729' with 2.6.16-rc4 kernel. A
>> simple solution is to use proper flags in __get_vm_area_node,
>> depending on the context:
> vmalloc sleeps, or at least does things to the lower vm layers
> that really do sleepy things. So calling it from an atomic
> context really tends to be a bug....
> where in the kernel is this done?
It is not about vmalloc, but about __vmalloc. I gave more details in
response to Nick Piggin's reply on this thread.
Thanks,
Giri
next prev parent reply other threads:[~2006-05-22 6:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 1:36 Giridhar Pemmasani
2006-05-22 1:51 ` Arjan van de Ven
2006-05-22 6:01 ` Giridhar Pemmasani [this message]
2006-05-22 1:53 ` Nick Piggin
2006-05-22 5:58 ` Giridhar Pemmasani
2006-05-22 6:07 ` Nick Piggin
2006-05-22 6:10 ` Nick Piggin
2006-05-22 6:14 ` Nick Piggin
2006-05-22 7:08 ` Giridhar Pemmasani
2006-05-22 7:34 ` Nick Piggin
2006-05-22 14:55 ` Giridhar Pemmasani
2006-05-22 6:56 ` Giridhar Pemmasani
2006-05-22 21:56 ` Andrew Morton
2006-05-22 22:59 ` Giridhar Pemmasani
2006-05-22 11:18 ` Andi Kleen
2006-05-22 15:12 ` Giridhar Pemmasani
2006-05-22 11:47 ` Alan Cox
2006-10-23 6:13 Giridhar Pemmasani
2006-10-23 10:38 ` Alan Cox
2006-10-23 11:11 ` Giridhar Pemmasani
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=20060522060133.91683EE9EE@wolfe.lmc.cs.sunysb.edu \
--to=giri@lmc.cs.sunysb.edu \
--cc=arjan@infradead.org \
--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
all inboxes | Powered by JetHome®