This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Multithread fork and atfork handlers
- From: Florian Weimer <fweimer at redhat dot com>
- To: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Wed, 31 Jan 2018 15:21:54 +0100
- Subject: Re: Multithread fork and atfork handlers
- Authentication-results: sourceware.org; auth=none
- References: <823ddb30-4ca6-6070-990c-f65e43c8b23c@linaro.org>
On 01/31/2018 03:17 PM, Adhemerval Zanella wrote:
The question is whether we still care for fork in mulithread performance
and if the possible stack overflow in its call call pays off.
Don't we already acquire locks around the fork system call? Not just
for malloc, but for libio's benefit as well?
Then the additional lock for the handler list should not matter.
Thanks,
Florian