Nick Piggin wrote:
OTOH, it doesn't seem to be particularly wrong to allow __vmalloc GFP_ATOMIC allocations. The correct fix is to pass the gfp_mask to kmalloc: if you're worried about breaking the API, introduce a new __get_vm_area_node_mask() and implement __get_vm_area_node() as a simple wrapper that passes in GFP_KERNEL.
Oh, and __get_vm_area_node{_mask} should BUG_ON(in_interrupt());
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
-
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]>
- Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
- References:
- __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
- From: Giridhar Pemmasani <[email protected]>
- Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
- From: Nick Piggin <[email protected]>
- Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
- From: Giridhar Pemmasani <[email protected]>
- Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
- From: Nick Piggin <[email protected]>
- Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
- From: Nick Piggin <[email protected]>
- __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
- Prev by Date: Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
- Next by Date: [PATCH 000 of 2] md: Introduction
- Previous by thread: Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
- Next by thread: Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
- Index(es):
 |