Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755527AbYH0L7c (ORCPT ); Wed, 27 Aug 2008 07:59:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753717AbYH0L7W (ORCPT ); Wed, 27 Aug 2008 07:59:22 -0400 Received: from smtp4.pp.htv.fi ([213.243.153.38]:43412 "EHLO smtp4.pp.htv.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753305AbYH0L7V (ORCPT ); Wed, 27 Aug 2008 07:59:21 -0400 Date: Wed, 27 Aug 2008 14:58:30 +0300 From: Adrian Bunk To: Linus Torvalds Cc: Rusty Russell , "Alan D. Brunelle" , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , Andrew Morton , Arjan van de Ven , Ingo Molnar , linux-embedded@vger.kernel.org Subject: Re: [Bug #11342] Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected Message-ID: <20080827115829.GF11734@cs181140183.pp.htv.fi> References: <200808261111.19205.rusty@rustcorp.com.au> <20080826183051.GB10925@cs181140183.pp.htv.fi> <20080826205916.GB11734@cs181140183.pp.htv.fi> <20080826232411.GC11734@cs181140183.pp.htv.fi> <20080827002316.GE11734@cs181140183.pp.htv.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1414 Lines: 44 On Tue, Aug 26, 2008 at 05:28:37PM -0700, Linus Torvalds wrote: > > > On Wed, 27 Aug 2008, Adrian Bunk wrote: > > > > When did we get callpaths like like nfs+xfs+md+scsi reliably > > working with 4kB stacks on x86-32? > > XFS may never have been usable, but the rest, sure. > > And you seem to be making this whole argument an excuse to SUCK, adn an > excuse to let gcc crap even more on our stack space. > > Why? > > Why aren't you saying that we should be able to do better? Instead, you > seem to asking us to do even worse than we do now? My main point is: - getting 4kB stacks working reliably is a hard task - having an eye on gcc increasing the stack usage, and fixing it if required, is relatively easy If we should be able to do better at getting (and keeping) 4kB stacks working, then coping with possible inlining problems caused by gcc should not be a big problem for us. > Linus cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- 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/