From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id pBC90bXt085721 for ; Mon, 12 Dec 2011 03:00:38 -0600 Received: from ipmail06.adl2.internode.on.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 7D5D2129971A for ; Mon, 12 Dec 2011 01:00:35 -0800 (PST) Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [150.101.137.129]) by cuda.sgi.com with ESMTP id 7e8Y0AjkPw4Lbf1S for ; Mon, 12 Dec 2011 01:00:35 -0800 (PST) Date: Mon, 12 Dec 2011 20:00:33 +1100 From: Dave Chinner Subject: Re: XFS causing stack overflow Message-ID: <20111212090033.GQ14273@dastard> References: <20111209115513.GA19994@infradead.org> <20111209221956.GE14273__25752.826271537$1323469420$gmane$org@dastard> <20111210221345.GG14273@dastard> <20111211000036.GH24062@one.firstfloor.org> <20111211230511.GH14273@dastard> <20111212023130.GI24062@one.firstfloor.org> <20111212043657.GO14273@dastard> <20111212051311.GJ24062@one.firstfloor.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20111212051311.GJ24062@one.firstfloor.org> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Andi Kleen Cc: Christoph Hellwig , linux-mm@kvack.org, "Ryan C. England" , xfs@oss.sgi.com On Mon, Dec 12, 2011 at 06:13:11AM +0100, Andi Kleen wrote: > > It's ~180 bytes, so it's not really that small. > > Quite small compared to what real code uses. And also fixed > size. > > > > > > is on the new stack. ISTs are not used for interrupts, only for > > > some special exceptions. > > > > IST = ??? > > That's a hardware mechanism on x86-64 to switch stacks > (Interrupt Stack Table or somesuch) > > With ISTs it would have been possible to move the the pt_regs too, > but the software mechanism is somewhat simpler. > > > at the top of the stack frame? Is the stack unwinder walking back > > across the interrupt stack to the previous task stack? > > Yes, the unwinder knows about all the extra stacks (interrupt > and exception stacks) and crosses them as needed. > > BTW I suppose it wouldn't be all that hard to add more stacks and > switch to them too, similar to what the 32bit do_IRQ does. > Perhaps XFS could just allocate its own stack per thread > (or maybe only if it detects some specific configuration that > is known to need much stack) That's possible, but rather complex, I think. > It would need to be per thread if you could sleep inside them. Yes, we'd need to sleep, do IO, possibly operate within a transaction context, etc, and a workqueue handles all these cases without having to do anything special. Splitting the stack at a logical point is probably better, such as this patch: http://oss.sgi.com/archives/xfs/2011-07/msg00443.html Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs