This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] attr.c in _STACK_GROWS_UP case.

From: Carlos O'Donell <carlos at baldric dot uwo dot ca>
To: Roland McGrath <roland at redhat dot com>
Cc: libc-alpha <libc-alpha at sources dot redhat dot com>
Date: Sun, 28 Dec 2003 18:55:57 -0500
Subject: Re: [PATCH] attr.c in _STACK_GROWS_UP case.
References: <20031228231554.GB27911@systemhalted> <200312282332.hBSNWquf010121@magilla.sf.frob.com>

On Sun, Dec 28, 2003 at 03:32:52PM -0800, Roland McGrath wrote:
> Don't you still need to do something to cap the size when the rlimit is
> very high (e.g. ulimit -s unlimited)?

Unknown. I just assume that you get to keep allocating stack until you
run off the end of the mapping and fault.

Shouldn't everyone be capping this to the other end of the vma?

e.g. 
      attr->__stacksize = (size_t)to - (size_t)from;

c.

Follow-Ups:
- Re: [PATCH] attr.c in _STACK_GROWS_UP case.
  - From: Jakub Jelinek

References:
- [PATCH] attr.c in _STACK_GROWS_UP case.
  - From: Carlos O'Donell
- Re: [PATCH] attr.c in _STACK_GROWS_UP case.
  - From: Roland McGrath

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]