Subject: Re: kernel stack overflow detection
To: None <firstname.lastname@example.org, email@example.com>
From: Kamal Prasad <firstname.lastname@example.org>
Date: 05/30/2002 11:22:38
in the absence of a swap device, how does one prevent
resource(memory) starvation and hence a deadlock under
UVM? is it possible that a ramdisk will aggrevate a
--- email@example.com wrote:
> At Thu, 30 May 2002 14:05:43 +0000 (UTC), "YAMAMOTO
> Takashi" wrote:
> > comments?
> you've given yourself an extra page, so fill it all
> with the magic
> number. It's possible for a stack overflow to get
> 'lucky' and miss
> a single magic location.
> Actually, while you're at it...
> You might provide a more generally-useful mechanism
> for debugging and
> system analysis:
> * fill _all_ kernel stack areas _completely_ with a
> magic number, and
> * provide a mechanism to check all of them to see
> how much has been
> (VxWorks provides a similar facility.) I don't know
> that anybody's
> really looked at the actual kernel stack usage on
> most ports...
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup