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)
On 10/05/2017 09:02 AM, Andreas Schwab wrote:
> On Okt 05 2017, Florian Weimer <fweimer@redhat.com> wrote:
>
>> I assumed you were arguing the patch was somehow okay because we used to
>> have the corruption bug.
>
> I was just stating a fact. Both problems are bad enough.
Either the user coordinated the threads to avoid the situation of having
a thread in dlopen while another thread calls fork, *or* it did not avoid
this problem and you end up with a deadlock.
Either way there is no reason to apply your patch? Why do you want to clear
the lock on fork? Just so you can access potentially corrupt data?
--
Cheers,
Carlos.