lkml.org 
[lkml]   [2002]   [Oct]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] (3/3) stack overflow checking for x86
Dave 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.

Greg KH just pointed out that someone else snuck in an overflow check.
However, they take completely different approaches. The Ben LaHaise
one that I posted uses GCC features to check the stack on entry to all
functions. The one in the tree now is much, much simpler than Ben's,
but only works only for detecting problems at the time that an
interrupt actually occurs.

--
Dave Hansen
haveblue@us.ibm.com

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

\
 
 \ /
  Last update: 2005-03-22 13:30    [W:2.184 / U:0.208 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site