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

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?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
    • From: Giridhar Pemmasani <[email protected]>

• References:
  • __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
    • From: Giridhar Pemmasani <[email protected]>

• Prev by Date: Re: [IDEA] Poor man's UPS
• Next by Date: Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
• Previous by thread: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
• Next by thread: Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]