Re: [PATCH] (3/3) stack overflow checking for x86

From: Dave Jones (davej@codemonkey.org.uk)
Date: Thu Oct 31 2002 - 16:30:32 EST

Next message: Philippe Troin: "sparc32: oops when writing to block devices"
Previous message: Greg KH: "Re: bare pci configuration access functions ?"
In reply to: David C. Hansen: "[PATCH] (3/3) stack overflow checking for x86"
Next in thread: David C. Hansen: "Re: [PATCH] (3/3) stack overflow checking for x86"
Reply: David C. Hansen: "Re: [PATCH] (3/3) stack overflow checking for x86"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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

Next message: Philippe Troin: "sparc32: oops when writing to block devices"
Previous message: Greg KH: "Re: bare pci configuration access functions ?"
In reply to: David C. Hansen: "[PATCH] (3/3) stack overflow checking for x86"
Next in thread: David C. Hansen: "Re: [PATCH] (3/3) stack overflow checking for x86"
Reply: David C. Hansen: "Re: [PATCH] (3/3) stack overflow checking for x86"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Oct 31 2002 - 22:00:56 EST