This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 1/2] Set default stack size from program environment
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: Siddhesh Poyarekar <siddhesh at redhat dot com>, libc-alpha at sourceware dot org
- Date: Fri, 1 Mar 2013 13:02:46 -0800 (PST)
- Subject: Re: [PATCH 1/2] Set default stack size from program environment
- References: <20130115100110.GL7894@spoyarek.pnq.redhat.com><20130117000752.EFE8D2C0BC@topped-with-meat.com><20130117014821.GX7894@spoyarek.pnq.redhat.com><mvm1udk5iul.fsf@hawking.suse.de><20130117082311.GB25252@spoyarek.pnq.redhat.com><mvmwqvc43jy.fsf@hawking.suse.de><20130117083500.GC25252@spoyarek.pnq.redhat.com><mvm4nig2o6p.fsf@hawking.suse.de>
> Does that means this affects all processes in the system? That's even
> worse than an environment variable.
It's worse in some regards and better in others. Anything overly
coarse-grained like system-wide configuration when it can be local
per-user or per-process/inherited configuration is worse for the
issues of user choice and flexibility. Conversely, anything only
changeable by privileged administrator action rather than inherited
from something casually fungible like the environment is better for
the issue of security hardening.