lkml.org 
[lkml]   [2001]   [May]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8
Date
On Fri, 25 May 2001 10:14:57 +0200, 
Andi Kleen <ak@suse.de> wrote:
>On Fri, May 25, 2001 at 03:20:20PM +1000, Keith Owens wrote:
>> You cannot recover from a kernel stack overflow even with kdb. The
>> exception handler and kdb use the stack that just overflowed.
>
>Hmm, I thought it used an own stack using an appropiate gate.
>At least on x86-64 I implemented it this way using a static 4K array.

Nothing in arch/i386/kernel/traps.c uses a task gate, they are all
interrupt, trap, system or call gates. I guarantee that kdb on ix86
and ia64 uses the same kernel stack as the failing task, the starting
point for the kdb backtrace is itself and it does not follow segment
switches.

-
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 12:53    [W:0.114 / U:0.172 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site