Re: Stack growth direction to thwart buffer overflow attacks

From: Sander Vesik (sander_at_haldjas.folklore.ee)
Date: 08/15/03 

Date: Fri, 15 Aug 2003 13:12:43 +0000 (UTC)

In comp.arch Nick Maclaren <nmm1@cus.cam.ac.uk> wrote:
>
>
> It is a good point, in that a common problem of using a stack is
> forgetting to check for stack overflow. But, equally, a common
> problem of static allocation is forgetting that and recursing.
> TANSTAAFL.

But not having stack doesn't mean you have to use static allocation -
you could use dynamic allocation for all memory needs. it would mean
that the C runtime would be a bit thicker than it could be otherwise,
but its not clear if 'as thin as possible' C runtime is a worthwhile
goal in many cases.

>
> Regards,
> Nick Maclaren. 

-- 
	Sander
+++ Out of cheese error +++

Relevant Pages

  • Re: Stack growth direction to thwart buffer overflow attacks
    ... |>> It is a good point, in that a common problem of using a stack is ... |>> forgetting to check for stack overflow. ... |>> problem of static allocation is forgetting that and recursing. ... |> you could use dynamic allocation for all memory needs. ...
    (comp.security.misc)
  • Re: Stack growth direction to thwart buffer overflow attacks
    ... |>> It is a good point, in that a common problem of using a stack is ... |>> forgetting to check for stack overflow. ... |>> problem of static allocation is forgetting that and recursing. ... |> you could use dynamic allocation for all memory needs. ...
    (comp.security.unix)
  • Re: Stack growth direction to thwart buffer overflow attacks
    ... > It is a good point, in that a common problem of using a stack is ... > forgetting to check for stack overflow. ... > problem of static allocation is forgetting that and recursing. ... But not having stack doesn't mean you have to use static allocation - ...
    (comp.security.unix)
  • Re: Why are variables stored on the stack?
    ... doesn't use a stack for the local variables. ... If an implementation uses static allocation for all local objects, ... It could still conform to the C standard if it uses static allocation ...
    (comp.lang.c)
  • Re: [PATCH 1/11] Add generic helpers for arch IPI function calls
    ... The waiter must also free the object, ... since now the callee does not. ... the caller will have it on the stack. ... suggest you get rid of the static allocation, and just turn it into a wait ...
    (Linux-Kernel)