As fixing it will very likely require a major rethinking of the locking strategy for the entire UST, I'm not very keen to make that kind of change within stable versions.
Unless an elegant solution shows up by tomorrow, I plan to disable the feature (leaving the code there), and think up a solution for 2.5. Thoughts ? Thanks, Mathieu ----- Original Message ----- > From: "Alexandre Montplaisir" <[email protected]> > To: "Mathieu Desnoyers" <[email protected]> > Cc: "Paul Woegerer" <[email protected]>, [email protected] > Sent: Thursday, February 27, 2014 6:37:23 PM > Subject: Re: [lttng-dev] baddr feature triggers deadlock in lttng-ust > > Could it be hidden behind a non-default configure option, instead of > completely removed? > > Alex > > > On 14-02-27 04: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 > > > > -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
