Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755069Ab1EDTDP (ORCPT ); Wed, 4 May 2011 15:03:15 -0400 Received: from smtp-out.google.com ([74.125.121.67]:9693 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754848Ab1EDTDO (ORCPT ); Wed, 4 May 2011 15:03:14 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version:content-type; b=G8ZYD4nydn318kKE70axuZURCc8c1E6FuwqKfo9fib5TK1W4rD3pYx48F35mtrIKq2 Zhaw+dQb5yWzQYRNxa4w== Date: Wed, 4 May 2011 12:03:08 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Christoph Lameter cc: Geert Uytterhoeven , James Bottomley , Linus Torvalds , Andrew Morton , Pekka Enberg , linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [git pull] m68k SLUB fix for 2.6.39 In-Reply-To: Message-ID: References: <1304026464.2598.36.camel@mulgrave.site> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1346 Lines: 26 On Wed, 4 May 2011, Christoph Lameter wrote: > As i have explained multiple times before: This is a generic issue with a > kernel configuration that has DISCONTIGMEM on and NUMA configured off. > Core code in various subsystems makes various assumptions in the !NUMA > case. F.e. page_to_nid(page) == 0. Slub is one of them. > Agreed, but James is still reporting that there is a slub oops with at least parisc even with the N_NORMAL_MEMORY fix applied. He's currently retrying on a clean kernel with the latest git (and presumably CONFIG_BROKEN to enable CONFIG_SLUB). If he reports that slub is no longer an issue with such a configuration, then I agree that we can remove the Kconfig change for slub so it no longer forces CONFIG_NUMA for CONFIG_DISCONTIGMEM (or CONFIG_BROKEN). If that's the case, and we'll have to wait for James' report back first, then we can probably make adjustments in the per-arch Kconfigs that enable discontigmem without NUMA and then make it a strict requirement (or CONFIG_BROKEN) until the additional problems are solved in other places in the kernel. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/