This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Consensus: Tuning runtime behaviour with environment variables.
- From: Rich Felker <dalias at aerifal dot cx>
- To: Siddhesh Poyarekar <siddhesh at redhat dot com>
- Cc: KOSAKI Motohiro <kosaki dot motohiro at gmail dot com>, libc-alpha at sourceware dot org
- Date: Thu, 30 May 2013 09:21:06 -0400
- Subject: Re: Consensus: Tuning runtime behaviour with environment variables.
- References: <51A58A92 dot 4050508 at redhat dot com> <51A653DC dot 4040702 at gmail dot com> <20130530071022 dot GN2145 at spoyarek dot pnq dot redhat dot com>
On Thu, May 30, 2013 at 12:40:22PM +0530, Siddhesh Poyarekar wrote:
> Speaking of which, it doesn't look like the environment variable write
> lock is reset at fork. There may be a chance at a deadlock if the
> process forked in the middle of a setenv and the child tried to
> setenv. But I digress...
After fork from a multithreaded process, you're in an async signal
context, i.e. you can only legally call async-signal-safe functions.
Rich