> > You could experiment by initializing the stack such that only a portion
> > was used. For example, allocate 4K, allocate kernel stuff, and then set
> > the pointers such that only 1K is available for use. That would expose
> > the memory hogs quickly. That is a pure debug case, of coruse.
>
> This is IMHO an extreme bad idea. The solution without crashing:
> init: alloc stack, fill with a magic (ex.: 0xdeadbeef)
> destroy: scan for magic on stack to calculate stackspace
The code is already in the kernel; it just assumes that the kernel stack
is being cleared with zero before use.
Ralf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu