From: Lucio Correia <ljhc@br.ibm.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Michael Ellerman <michael@ellerman.id.au>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arndb@arndb.de>
Subject: Re: SLUB doesn't work with kdump kernel on Cell
Date: Wed, 15 Aug 2007 16:57:12 -0300 [thread overview]
Message-ID: <1187207832.3002.4.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0708141910230.1409@schroedinger.engr.sgi.com>
On Tue, 2007-08-14 at 19:11 -0700, Christoph Lameter wrote:
> Can you try this patch?
Thanks, Christoph
It worked fine, both for normal kernel and for dump kernel on Cell. Is
this patch intended to go mainline?
>
> From 74863f472810cb58dc56dde050616581d38f7673 Mon Sep 17 00:00:00 2001
> From: Christoph Lameter <christoph@qirst.com>
> Date: Tue, 14 Aug 2007 19:09:00 -0700
> Subject: [PATCH] SLUB: Do not fail on broken memory configurations
>
> Print a big fat warning and do what is necessary to continue if a node
> is marked as up but allocations from the node do not succeed.
>
> Signed-off-by: Christoph Lameter <clameter@sgi.com>
> ---
> mm/slub.c | 11 +++++++++--
> 1 files changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/mm/slub.c b/mm/slub.c
> index 1488e71..fc82751 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -1877,9 +1877,16 @@ static struct kmem_cache_node * __init early_kmem_cache_node_alloc(gfp_t gfpflag
>
> BUG_ON(kmalloc_caches->size < sizeof(struct kmem_cache_node));
>
> - page = new_slab(kmalloc_caches, gfpflags | GFP_THISNODE, node);
> -
> + page = new_slab(kmalloc_caches, gfpflags, node);
> BUG_ON(!page);
> +
> + if (page_to_nid(page) != node) {
> + printk(KERN_ERR "SLUB: Unable to allocate memory from "
> + "node %d\n", node);
> + printk(KERN_ERR "SLUB: Allocating a useless per node structure"
> + " in order to be able to continue\n");
> + }
> +
> n = page->freelist;
> BUG_ON(!n);
> page->freelist = get_freepointer(kmalloc_caches, n);
--
Lucio Correia
Software Engineer
IBM LTC Brazil
next prev parent reply other threads:[~2007-08-15 19:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 20:15 SLUB doesn't work with kdump kernel on Cell Lucio Correia
2007-08-08 20:26 ` Christoph Lameter
2007-08-08 20:34 ` Arnd Bergmann
2007-08-08 20:39 ` Christoph Lameter
2007-08-14 15:43 ` Lucio Correia
2007-08-14 19:42 ` Christoph Lameter
2007-08-15 0:57 ` Michael Ellerman
2007-08-15 1:56 ` Christoph Lameter
2007-08-15 2:11 ` Christoph Lameter
2007-08-15 19:57 ` Lucio Correia [this message]
2007-08-15 20:21 ` Christoph Lameter
2007-08-08 21:10 ` Arnd Bergmann
2007-08-09 13:57 ` Lucio Correia
2007-08-10 0:34 ` Michael Ellerman
2007-08-10 15:43 ` [Cbe-oss-dev] " Arnd Bergmann
2007-08-10 0:26 ` Michael Ellerman
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=1187207832.3002.4.camel@localhost.localdomain \
--to=ljhc@br.ibm.com \
--cc=arndb@arndb.de \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.