[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1202061358170.3817@chino.kir.corp.google.com>
Date: Mon, 6 Feb 2012 13:58:56 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: Willy Tarreau <w@....eu>
cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Pekka Enberg <penberg@...nel.org>,
James Bottomley <James.Bottomley@...e.de>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 02/91] slub: fix panic with DISCONTIGMEM
On Sun, 5 Feb 2012, Willy Tarreau wrote:
> commit 4a5fa3590f09999f6db41bc386bce40848fa9f63 upstream.
>
> Slub makes assumptions about page_to_nid() which are violated by
> DISCONTIGMEM and !NUMA. This violation results in a panic because
> page_to_nid() can be non-zero for pages in the discontiguous ranges and
> this leads to a null return by get_node(). The assertion by the
> maintainer is that DISCONTIGMEM should only be allowed when NUMA is also
> defined. However, at least six architectures: alpha, ia64, m32r, m68k,
> mips, parisc violate this. The panic is a regression against slab, so
> just mark slub broken in the problem configuration to prevent users
> reporting these panics.
>
> Acked-by: David Rientjes <rientjes@...gle.com>
> Acked-by: Pekka Enberg <penberg@...nel.org>
> Signed-off-by: James Bottomley <James.Bottomley@...e.de>
> Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>
The problem that this patch initially addressed is fixed by the next patch
in your series, "set memory ranges in N_NORMAL_MEMORY when onlined", so I
don't think this one should be merged.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists