From: Dave Jones <davej@codemonkey.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "David C. Hansen" <haveblue@us.ibm.com>,
Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] (3/3) stack overflow checking for x86
Date: Fri, 1 Nov 2002 13:42:38 +0000 [thread overview]
Message-ID: <20021101134238.GA23904@suse.de> (raw)
In-Reply-To: <1036155546.12551.3.camel@irongate.swansea.linux.org.uk>
On Fri, Nov 01, 2002 at 12:59:06PM +0000, Alan Cox wrote:
> On Thu, 2002-10-31 at 21:30, Dave Jones wrote:
> > > 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 ?
>
> It replaces it and actually makes it useful since IRQ usage is now
> bounded and defined relative to non IRQ usage. Without IRQ stacks you
> don't have a hope in hell of catching overflows that depend on an irq
> occuring at the right moment
Yeah, I figured it worked better, but wondered why the patch didn't
remove the existing implementation.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-11-01 13:37 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
2002-10-31 22:08 ` David C. Hansen
2002-11-01 12:59 ` Alan Cox
2002-11-01 13:42 ` Dave Jones [this message]
-- 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=20021101134238.GA23904@suse.de \
--to=davej@codemonkey.org.uk \
--cc=alan@lxorguk.ukuu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox