From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: [Bug #11342] Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected Date: Tue, 26 Aug 2008 12:09:46 -0700 (PDT) Message-ID: References: <48B29F7B.6080405@hp.com> <48B2A421.7080705@hp.com> <48B313E0.1000501@hp.com> <48B452F3.9040304@sgi.com> Mime-Version: 1.0 Return-path: In-Reply-To: <48B452F3.9040304-sJ/iWh9BUns@public.gmane.org> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: TEXT/PLAIN; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Mike Travis 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 , Andrew Morton , Christoph Lameter 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