From: Dave Jones <davej@codemonkey.org.uk>
To: "David C. Hansen" <haveblue@us.ibm.com>
Cc: Linus Torvalds <torvalds@transmeta.COM>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] (3/3) stack overflow checking for x86
Date: Thu, 31 Oct 2002 21:30:32 +0000 [thread overview]
Message-ID: <20021031213032.GA25685@suse.de> (raw)
In-Reply-To: <1036092052.4272.96.camel@nighthawk>
On Thu, Oct 31, 2002 at 11:20:52AM -0800, David C. Hansen wrote:
> * stack checking (3/3)
> - use gcc's profiling features to check for stack overflows upon
> entry to functions.
> - Warn if the task goes over 4k.
> - Panic if the stack gets within 512 bytes of overflowing.
> - use kksymoops information, if available
>
> This won't apply cleanly without the irqstack patch, but the conflict is
> easy to resolve. It requires the thread_info cleanup.
I'm wondering about interaction between this patch and the
already merged CONFIG_DEBUG_STACKOVERFLOW ?
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-10-31 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 19:18 [PATCH] (1/3) cleanup thread info on x86 David C. Hansen
2002-10-31 19:20 ` [PATCH] (2/3) per-cpu interrupt stacks for x86 David C. Hansen
2002-10-31 19:20 ` [PATCH] (3/3) stack overflow checking " David C. Hansen
2002-10-31 21:30 ` Dave Jones [this message]
2002-10-31 22:08 ` David C. Hansen
2002-11-01 12:59 ` Alan Cox
2002-11-01 13:42 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2002-10-18 22:07 Dave Hansen
2002-10-18 22:31 ` Dave Hansen
2002-10-18 22:48 ` Andreas Dilger
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=20021031213032.GA25685@suse.de \
--to=davej@codemonkey.org.uk \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.COM \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.