Date: Fri, 1 Apr 2005 13:09:42 -0600
From: Terence Ripperda <tripperda@nvidia.com>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Terence Ripperda <tripperda@nvidia.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: question about do_IRQ + 4k stacks
Message-ID: <20050401190942.GC2104@hygelac>
Reply-To: Terence Ripperda <tripperda@nvidia.com>
References: <20050330221042.GZ2104@hygelac> <424B5CFE.6010907@didntduck.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <424B5CFE.6010907@didntduck.org>
User-Agent: Mutt/1.5.6+20040907i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 758
Lines: 21

On Wed, Mar 30, 2005 at 09:14:22PM -0500, bgerst@didntduck.org wrote:
> It checks for both process context (system call or kernel thread) or 
> interrupt context (nested irqs) stack overflows.

ok, thanks. 

so we really only have 3k stacks rather than 4k stacks, right? if any
code exceeds 3k stacks and is preempted by an interrupt, we can
trigger this check and hang the system as a result (I notice that at
least RHEL 4's kernels enable this check by default, not sure about
other kernels).

Thanks,
Terence


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