Date: Thu, 14 Jan 2016 21:47:59 -0500 From: Rich Felker <dalias@...c.org> To: musl@...ts.openwall.com Subject: Re: dlopen deadlock On Fri, Jan 15, 2016 at 01:31:49AM +0100, Szabolcs Nagy wrote: > * 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) > > > > the multi-threadedness detection is also problematic in > > > do_init_fini: > > > > > > need_locking = has_threads > > > if (need_locking) > > > lock(init_fini_lock) > > > for all deps > > > run_ctors(dep) > > > if (!need_locking && has_threads) > > > need_locking = 1 > > > lock(init_fini_lock) > > > if (need_locking) > > > unlock(init_fini_lock) > > > > > > checking for threads after ctors are run is too late if > > > the ctors may start new threads that can dlopen libs with > > > common deps with the currently loaded lib. > > > > The logic seems unnecessary now that there's no lazy/optional thread > > pointer initialization (originally it was a problem because > > pthread_mutex_lock with a recursive mutex needed to access TLS for the > > owner tid, but TLS might not have been initialized when the ctors ran) > > but I don't immediately see how it's harmful. The only state the lock > > protects is p->constructed and the fini chain (fini_head, > > p->fini_next) which are all used before the ctors run. The need for > > locking is re-evaluated after the ctors run. > > > > hm ok > i thought the ctors of the same lib might end up being > called twice, concurrently, but i see p->constructed > protects against that > > > > one solution i can think of is to have an init_fini_lock > > > for each dso, then the deadlock only happens if a ctor > > > tries to dlopen its own lib (directly or indirectly) > > > which is nonsense (the library depends on itself being > > > loaded) > > > > The lock has to protect the fini chain linked list (used to control > > order of dtors) so I don't think having it be per-dso is a > > possibility. > > > > i guess using lockfree atomics could solve the deadlock then I don't think atomics help. We could achieve the same thing as atomics by just taking and releasing the lock on each iteration when modifying the lock-protected state, but not holding the lock while calling the actual ctors. >From what I can see/remember, the reason I didn't write the code that way is that we don't want dlopen to return before all ctors have run -- or at least started running, in the case of a recursive call to dlopen. If the lock were taken/released on each iteration, two threads simultaneously calling dlopen on the same library libA that depends on libB could each run A's ctors and B's ctors and either of them could return from dlopen before the other finished, resulting in library code running without its ctors having finished. The problem is that excluding multiple threads from running possibly-unrelated ctors simultaneously is wrong, and marking a library constructed as soon as its ctors start is also wrong (at least once this big-hammer lock is fixed). Instead we should be doing some sort of proper dependency-graph tracking and ensuring that a dlopen cannot return until all dependencies have completed their ctors, except in the special case of recursion, in which case it's acceptable for libX's ctors to load a libY that depends on libX, where libX should be treated as "already constructed" (it's a bug in libX if it has not already completed any initialization that libY might depend on). However I don't see any reasonable way to track this kind of relationship when it happens 'indirectly-recursively' via a new thread. It may just be that such a case should deadlock. However, dlopen of separate libs which are unrelated in any dependency sense to the caller should _not_ deadlock just because it happens from a thread created by a ctor... Rich
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.