lkml.org 
[lkml]   [1999]   [Mar]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: tracing a kernel stack corruption
two questions:

1. a function call a function which call another function and so on. how
can we be sure not to go beyond 7k ? there is a automatic detection of
this, a log/oops or other ?

2. why only 7k when a typical kernel uses 2meg ?

On Tue, Mar 23, 1999 at 02:17:43PM +0100, Ingo Molnar wrote:
> One important kernel programming rule, at most ~7K should be used as stack
> variables. (~4k on 2.0, thus a good guideline is to never allocate more
> than 3k). Most probably the problem is that you allocate some big
> structure on the kernel stack:


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

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