Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750759AbVLTCww (ORCPT ); Mon, 19 Dec 2005 21:52:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750761AbVLTCww (ORCPT ); Mon, 19 Dec 2005 21:52:52 -0500 Received: from rtr.ca ([64.26.128.89]:13038 "EHLO mail.rtr.ca") by vger.kernel.org with ESMTP id S1750759AbVLTCww (ORCPT ); Mon, 19 Dec 2005 21:52:52 -0500 Message-ID: <43A77205.2040306@rtr.ca> Date: Mon, 19 Dec 2005 21:52:53 -0500 From: Mark Lord User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051013 Debian/1.7.12-1ubuntu1 X-Accept-Language: en, en-us MIME-Version: 1.0 To: "J.A. Magallon" Cc: "Linux-Kernel, " , nel@vger.kernel.org Subject: Re: About 4k kernel stack size.... References: <20051218231401.6ded8de2@werewolf.auna.net> In-Reply-To: <20051218231401.6ded8de2@werewolf.auna.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 840 Lines: 23 J.A. Magallon wrote: > Hi... > > I'm following the intense thread about stack size, and I see only one > solution. > > Ship the nest stable, development, -mm, everything release of everything > with a maximum kernel/interrupt stack usage meter. The ask a poll for > everyone to send /proc/sys/stack_usage_max to a mailing list. That won't do it. The mainline code paths are undoubtedly fine with 4K stacks. It's the *error paths* that are most likely to go deeper on the stack, and those are rarely exercised by anyone. And those are the paths that we *really* need to be reliable. Cheers - 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/