This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Reinitialize dl_load_write_lock on fork (bug 19282)

From: Florian Weimer <fweimer at redhat dot com>
To: Andreas Schwab <schwab at suse dot de>, libc-alpha at sourceware dot org
Date: Thu, 5 Oct 2017 17:25:11 +0200
Subject: Re: [PATCH] Reinitialize dl_load_write_lock on fork (bug 19282)
Authentication-results: sourceware.org; auth=none
Authentication-results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=fweimer at redhat dot com
Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 46FAAC04AC4E
References: <mvm4lrd39p8.fsf@suse.de>

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 stateinstead of hanging. If not, this needs a comment why this does not happen.


Thanks,
Florian

Follow-Ups:
- Re: [PATCH] Reinitialize dl_load_write_lock on fork (bug 19282)
  - From: Andreas Schwab

References:
- [PATCH] Reinitialize dl_load_write_lock on fork (bug 19282)
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]