Fix: perform TLS fixup in all UST entry points from each thread
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Sat, 1 Oct 2016 22:59:17 +0000 (18:59 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Mon, 3 Oct 2016 15:47:11 +0000 (11:47 -0400)
commita3b964ebc0510bacc9af2d729f1a68c2e3ccc95d
treeb8cdaca2aea218467f0ac53eba6c1b820a815d44
parent38a7bf26121aa474821d215c4d8c583be531d40d
Fix: perform TLS fixup in all UST entry points from each thread

Each entry point into lttng-ust that end up taking the ust lock need to
perform a TLS fixup for each thread. Add a TLS fixup in both listener
threads, in fork and base address dump helper libs, and in app context
and tracepoint probe registration/unregistration functions, which can be
called from application threads.

Those ensure we don't take the libc dl lock within the ust lock when
performing the TLS lazy fixup.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
liblttng-ust/lttng-context-provider.c
liblttng-ust/lttng-probes.c
liblttng-ust/lttng-tracer-core.h
liblttng-ust/lttng-ust-comm.c
liblttng-ust/lttng-ust-statedump.c
This page took 0.026122 seconds and 4 git commands to generate.