Date: Wed, 23 Mar 2016 11:55:36 +0100 From: Szabolcs Nagy <nsz@...t70.net> To: musl@...ts.openwall.com Subject: Re: dlopen deadlock * Szabolcs Nagy <nsz@...t70.net> [2016-01-15 01:31:49 +0100]: > * Rich Felker <dalias@...c.org> [2016-01-14 17:41:15 -0500]: > > On Wed, Jan 13, 2016 at 12:09:37PM +0100, Szabolcs Nagy wrote: > > > This bug i reported against glibc also affects musl: > > > https://sourceware.org/bugzilla/show_bug.cgi?id=19448 > > > > > > in case of musl it's not the global load lock, but the > > > init_fini_lock that causes the problem. > > > > The deadlock happens when a ctor makes a thread that calls dlopen and > > does not return until the new thread's dlopen returns, right? > > > > yes > (not a common scenario) more general deadlock case: ctor waits for another thread that is in dlopen waiting for the init_fini_lock. this actually happened on glibc, but through interposed malloc instead of a ctor https://sourceware.org/ml/libc-alpha/2016-03/msg00594.html
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.