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
Date: Fri, 1 Apr 2005 13:09:42 -0600 [thread overview]
Message-ID: <20050401190942.GC2104@hygelac> (raw)
In-Reply-To: <424B5CFE.6010907@didntduck.org>
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
prev parent reply other threads:[~2005-04-01 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 22:10 question about do_IRQ + 4k stacks Terence Ripperda
2005-03-31 2:14 ` Brian Gerst
2005-04-01 19:09 ` Terence Ripperda [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050401190942.GC2104@hygelac \
--to=tripperda@nvidia.com \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox