Date: Sun, 03 Apr 2005 03:48:58 +0900 (JST)
Message-Id: <20050403.034858.70218818.ooyama@tritech.co.jp>
To: cw@f00f.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel stack size
From: ooyama eiichi <ooyama@tritech.co.jp>
In-Reply-To: <20050402182438.GA29095@taniwha.stupidest.org>
References: <20050402175345.GA28710@taniwha.stupidest.org>
	<20050403.031542.23015132.ooyama@tritech.co.jp>
	<20050402182438.GA29095@taniwha.stupidest.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1063
Lines: 34

> On Sun, Apr 03, 2005 at 03:15:42AM +0900, ooyama eiichi wrote:
> 
> > in i386 and ia64.
> 
> search for CONFIG_DEBUG_STACKOVERFLOW in arch/i386/kernel/irq.c

Oh, very good information for me.

> 
> ia64 has fairly large stacks so you probably won't need to check there
> if you get the above working

in ia64, he works properly.

> 
> > because my driver hungs the machine by an certain ioctl.  and it
> > seems to me there is no bad in the code correspond to the ioctl,
> > except for that it is using large auto variables.  (some functions
> > are useing ~1KB autos)
> 
> don't do that, even if you make it 'apparently' work for you it will
> just end up being a problem mater on or for someone else
> 

I changed these to using kmalloc().
(but not yet confirmed for my driver to work properly)

Thanks very much.

-
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/