From: Giridhar Pemmasani <giri@lmc.cs.sunysb.edu>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Slab panic on 2.6.19-rc3-git5 (-git4 was OK)
Date: Sun, 29 Oct 2006 15:53:12 -0500 [thread overview]
Message-ID: <ei34bo$dhr$1@sea.gmane.org> (raw)
In-Reply-To: <454471C3.2020005@yahoo.com.au>
Nick Piggin wrote:
> Andrew Morton wrote:
>> --- a/mm/vmalloc.c~__vmalloc_area_node-fix
>> +++ a/mm/vmalloc.c
>> @@ -428,7 +428,8 @@ void *__vmalloc_area_node(struct vm_stru
>> area->nr_pages = nr_pages;
>> /* Please note that the recursion is strictly bounded. */
>> if (array_size > PAGE_SIZE) {
>> - pages = __vmalloc_node(array_size, gfp_mask, PAGE_KERNEL, node);
>> + pages = __vmalloc_node(array_size, gfp_mask & ~__GFP_HIGHMEM,
>> + PAGE_KERNEL, node);
>> area->flags |= VM_VPAGES;
>> } else {
>> pages = kmalloc_node(array_size,
>
> Don't you actually *want* the page array to be allocated from highmem? So
> the gfp mask here should be just for whether we're allowed to sleep /
> reclaim (ie gfp_mask & ~(__GFP_DMA|__GFP_DMA32) | (__GFP_HIGHMEM))?
>
> Slab allocations should be (gfp_mask &
> ~(__GFP_DMA|__GFP_DMA32|__GFP_HIGHMEM)), which you could mask in
> __get_vm_area_node
>
Since gfp_mask there would also have GFP_ZERO, we need to mask off that too.
How about my earlier suggestion of masking off flags in __get_vm_area_node
with GFP_LEVEL_MASK?
Giri
PS: I am not sure if this mail gets to all recipients in the original
thread - I am not subscribed to lkml and I haven't found a way to reply to
all people and the group.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-10-29 21:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 5:57 Martin J. Bligh
2006-10-29 6:58 ` Pekka Enberg
2006-10-29 12:46 ` Giridhar Pemmasani
2006-10-29 15:21 ` Martin J. Bligh
2006-10-29 15:53 ` Giridhar Pemmasani
2006-10-29 7:05 ` Andrew Morton
2006-10-29 9:17 ` Nick Piggin
2006-10-29 20:53 ` Giridhar Pemmasani [this message]
2006-10-29 17:47 ` Andy Whitcroft
2006-10-29 22:59 ` Martin J. Bligh
2006-10-30 1:19 ` Linus Torvalds
2006-10-30 9:53 ` Andy Whitcroft
2006-10-30 15:35 ` Andy Whitcroft
2006-10-30 15:47 ` Pekka Enberg
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='ei34bo$dhr$1@sea.gmane.org' \
--to=giri@lmc.cs.sunysb.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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