[lttng-dev] baddr feature triggers deadlock in lttng-ust

[mathieu.desnoyers@efficios.com (Mathieu Desnoyers)]

----- Original Message -----
> From: "Paul Woegerer" <Paul_Woegerer@mentor.com>
> To: "Mathieu Desnoyers" <mathieu.desnoyers at efficios.com>, lttng-dev at lists.lttng.org, "CS ESD-Analyzer"
> <esd-analyzer at mentor.com>
> Sent: Friday, February 28, 2014 7:38:55 AM
> Subject: Re: baddr feature triggers deadlock in lttng-ust
> 
> I have looked a bit into the issue...
> 
> The ust_locking inside the dl_iterate_phdr triggers the deadlock.
> 
> If I just collect the base address info inside dl_iterate_phdr and dump
> the collected data with trace_baddr afterwards (outside the
> dl_iterate_phdr iteration) the deadlock will be prevented.
> 
> I'm now going to create a patch that implements this approach.

I suspect that having the UST lock nested inside the dynamic loader lock
only makes the problem happen more consistently, but that the basic issue
is that the dynamic loader lock should not be held while another thread
concurrently calls fork/clone/daemon. It seems to leave the child process
in a state where the lock state is stale (taken).

Thanks,

Mathieu

> 
> Thanks,
> Paul
> 
> On 02/27/2014 10:30 PM, Mathieu Desnoyers wrote:
> > Hi Paul,
> >
> > Please see http://bugs.lttng.org/issues/745, which explains a deadlock
> > we just found out.
> >
> > We might have to disable the baddr dump feature, since our release is
> > tomorrow. We'll have to re-think our locking to protect operations
> > using the dynamic loader lock against fork, clone, and daemon.
> >
> > Thanks,
> >
> > Mathieu
> >
> 
> 
> --
> Paul Woegerer, SW Development Engineer
> Sourcery Analyzer <http://go.mentor.com/sourceryanalyzer>
> Mentor Graphics, Embedded Software Division
> 
> 

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com