This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Multithread fork and atfork handlers
On 31/01/2018 12:21, Florian Weimer wrote:
> 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.
Indeed, I think we can go for the double-linked list and remove the list
lock-free complexity and alloca in fork.