Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760056AbYHZTfl (ORCPT ); Tue, 26 Aug 2008 15:35:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759072AbYHZTfU (ORCPT ); Tue, 26 Aug 2008 15:35:20 -0400 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:44077 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758956AbYHZTfS (ORCPT ); Tue, 26 Aug 2008 15:35:18 -0400 Message-ID: <48B45AF4.8040101@sgi.com> Date: Tue, 26 Aug 2008 12:35:16 -0700 From: Mike Travis User-Agent: Thunderbird 2.0.0.6 (X11/20070801) MIME-Version: 1.0 To: Linus Torvalds CC: "Alan D. Brunelle" , Ingo Molnar , Thomas Gleixner , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , Andrew Morton , Arjan van de Ven , Rusty Russell , "Siddha, Suresh B" , "Luck, Tony" , Jack Steiner , Christoph Lameter Subject: Re: [Bug #11342] Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected References: <48B29F7B.6080405@hp.com> <48B2A421.7080705@hp.com> <48B313E0.1000501@hp.com> <48B452F3.9040304@sgi.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1499 Lines: 39 Linus Torvalds wrote: > > On Tue, 26 Aug 2008, Mike Travis wrote: >> The need to allow distros to set NR_CPUS=4096 (and NODES_SHIFT=9) is >> critical to our upcoming SGI systems using what we have been calling >> "UV". > > That's fine. You can do it. The default kernel will not, because it's > clearly not safe. > > I really don't care what you do to _your_ images. But I will not > distribute a known-broken kernel, and I will not debug random stack > overflows that happen in it. > > If you want the default kernel to support 4k cores, we'll need to fix the > stack usage. I don't think that is impossible, but IT IS NOT GOING TO > HAPPEN for 2.6.27. > > And quite frankly, if some vendor like RedHat enables NR_CPUS=4096 by > default, they are totally and utterly crazy. > > But some SGI-specific binary that is meant for SGI machines only, and has > been extensively tested with the setup used on SGI machines is a different > thing. > > Linus Ok, thanks for the reply, and looking into this issue. We will "strongly encourage" our distros to base the relevant releases on 2.6.28. :-) [Supplying an SGI-specific kernel would not be acceptable to many of our customers because of the certification issues I mentioned.] Mike -- 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/