aboutsummaryrefslogtreecommitdiffstats
path: root/mm/vmalloc.c
diff options
context:
space:
mode:
authorGiridhar Pemmasani <pgiri@yahoo.com>2006-10-29 07:46:55 -0500
committerLinus Torvalds <torvalds@g5.osdl.org>2006-10-29 11:01:58 -0500
commit5211e6e6c671f0d4b1e1a1023384d20227d8ee65 (patch)
tree437c827044b2ed0a277adc95182985d8a95a8fc0 /mm/vmalloc.c
parent2da6dc28867b6cad6181291ed03093a487587d61 (diff)
[PATCH] Fix GFP_HIGHMEM slab panic
As reported by Martin J. Bligh <mbligh@google.com>, we let through some non-slab bits to slab allocation through __get_vm_area_node when doing a vmalloc. I haven't been able to reproduce this, although I understand why it happens: vmalloc allocates memory with GFP_KERNEL | __GFP_HIGHMEM and commit 52fd24ca1db3a741f144bbc229beefe044202cac resulted in the same flags are passed down to cache_alloc_refill, causing the BUG. The following patch fixes it. Note that when calling kmalloc_node, I am masking off __GFP_HIGHMEM with GFP_LEVEL_MASK, whereas __vmalloc_area_node does the same with ~(__GFP_HIGHMEM | __GFP_ZERO). IMHO, using GFP_LEVEL_MASK is preferable, but either should fix this problem. Signed-off-by: Giridhar Pemmasani (pgiri@yahoo.com) Cc: Martin J. Bligh <mbligh@google.com> Cc: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'mm/vmalloc.c')
-rw-r--r--mm/vmalloc.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 6d381df7c9b..46606c133e8 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -182,7 +182,7 @@ static struct vm_struct *__get_vm_area_node(unsigned long size, unsigned long fl
182 addr = ALIGN(start, align); 182 addr = ALIGN(start, align);
183 size = PAGE_ALIGN(size); 183 size = PAGE_ALIGN(size);
184 184
185 area = kmalloc_node(sizeof(*area), gfp_mask, node); 185 area = kmalloc_node(sizeof(*area), gfp_mask & GFP_LEVEL_MASK, node);
186 if (unlikely(!area)) 186 if (unlikely(!area))
187 return NULL; 187 return NULL;
188 188