Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'

[Giridhar Pemmasani <giri@lmc.cs.sunysb.edu>]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/