This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Reinitialize dl_load_write_lock on fork (bug 19282)
- From: Andreas Schwab <schwab at suse dot de>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Thu, 05 Oct 2017 17:39:29 +0200
- Subject: Re: [PATCH] Reinitialize dl_load_write_lock on fork (bug 19282)
- Authentication-results: sourceware.org; auth=none
- References: <mvm4lrd39p8.fsf@suse.de> <bf25f0c6-c70d-3672-03be-bd41b6b11bd1@redhat.com>
On Okt 05 2017, Florian Weimer <fweimer@redhat.com> wrote:
> On 10/05/2017 05:17 PM, Andreas Schwab wrote:
>> - /* Reset the lock the dynamic loader uses to protect its data. */
>> + /* Reset the locks the dynamic loader uses to protect its data. */
>> __rtld_lock_initialize (GL(dl_load_lock));
>> + __rtld_lock_initialize (GL(dl_load_write_lock));
>
> I'm pretty sure that the child now sees corrupted a dynamic linker state
> instead of hanging.
That's a good point, though this problem already existed before the
introduction of dl_load_write_lock.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."