[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 15 Jan 2016 11:58:19 +0100
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: dlopen deadlock
* Rich Felker <dalias@...c.org> [2016-01-14 21:47:59 -0500]:
> On Fri, Jan 15, 2016 at 01:31:49AM +0100, Szabolcs Nagy wrote:
> > 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.
>
ok then use cond vars:
for (; p; p=p->next) {
lock(m);
if (p->ctors_started) {
while (!p->ctors_done)
cond_wait(p->cond, m);
unlock(m);
continue;
}
p->ctors_started = 1;
// update fini_head...
unlock(m);
run_ctors(p); // no global lock is held
lock(m);
p->ctors_done = 1;
cond_broadcast(p->cond);
unlock(m);
}
> 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,
this works with cond vars.
> 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
this does not work.
> 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,
if the dso currently being constructed is stored in tls
and this info is passed down to every new thread then
dlopen could skip this dso.
of course there might be several layers of recursive
dlopen calls so it is a list of dsos under construction
so like
self = pthread_self();
for (; p; p=p->next) {
if (contains(self->constructing, p))
continue;
...
old = p->next_constructing = self->constructing;
self->constructing = p;
run_ctors(p);
self->constructing = old;
...
}
and self->constructing needs to be set up in pthread_create.
bit overkill for a corner case that never happens
but it seems possible to do.
> 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...
i think this works with the simple cond vars approach.
>
> 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.
