Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 20 Feb 2003 15:16:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 20 Feb 2003 15:16:07 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:52487 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Thu, 20 Feb 2003 15:15:09 -0500 Date: Thu, 20 Feb 2003 12:20:41 -0800 (PST) From: Linus Torvalds To: Alan Cox cc: "Martin J. Bligh" , Ingo Molnar , Dave Hansen , Zwane Mwaikambo , Chris Wedgwood , Linux Kernel Mailing List , William Lee Irwin III Subject: Re: doublefault debugging (was Re: Linux v2.5.62 --- spontaneous reboots) In-Reply-To: <1045776104.3790.34.camel@irongate.swansea.linux.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1689 Lines: 38 On 20 Feb 2003, Alan Cox wrote: > On Thu, 2003-02-20 at 16:54, Linus Torvalds wrote: > > Ok, the 4kB stack definitely won't work in real life, but that's because > > we have some hopelessly bad stack users in the kernel. But the debugging > > part would be good to try (in fact, it might be a good idea to keep the > > 8kB stack, but with rather anal debugging. Just the "mcount" part should > > do that). > > You also need IRQ stacks to get down to 4K. The wrong pattern of ten > different IRQ handlers using a mere 200 bytes each will eventually > happen and eventually kill you otherwise. Martin's patch set included the per-IRQ stacks, so that part should be ok. However, since even a single function will overflow the stack depth test of "half the stack", I'm just saying that right now the 4kB stacks obviously shouldn't be used for overflow testing (and the 8kB stack version right now is way too permissive). > > That ide_unregister() thing uses up >2kB in just one call! And there are > > several in the 1.5kB range too, with a long list of ~500 byte offenders. > > ide_unregister is a really stupid one. Its copying a struct mostly to > restore fields it shouldnt be restoring but should be setting in the > allocator. I hadn't realised quite how bad it was. Added to the ide > shitlist Well, ide_unregister() was only the worst of a fairly large bunch of crap. Although I guess nobody is really surprised. Linus - 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/