From: alexmonthy@voxpopuli.im (Alexandre Montplaisir)
Subject: [lttng-dev] baddr feature triggers deadlock in lttng-ust
Date: Thu, 27 Feb 2014 18:37:23 -0500 [thread overview]
Message-ID: <530FCC33.4050200@voxpopuli.im> (raw)
In-Reply-To: <561294755.31915.1393536606539.JavaMail.zimbra@efficios.com>
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
>
next prev parent reply other threads:[~2014-02-27 23:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1640835527.31912.1393536374130.JavaMail.zimbra@efficios.com>
2014-02-27 21:30 ` Mathieu Desnoyers
2014-02-27 23:37 ` Alexandre Montplaisir [this message]
2014-02-28 0:07 ` Mathieu Desnoyers
2014-02-28 9:33 ` Woegerer, Paul
2014-02-28 12:38 ` Woegerer, Paul
2014-02-28 14:05 ` Mathieu Desnoyers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=530FCC33.4050200@voxpopuli.im \
--to=alexmonthy@voxpopuli.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox