From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev <lttng-dev@lists.lttng.org>,
Diamon discuss <diamon-discuss@lists.linuxfoundation.org>,
linux-trace-users <linux-trace-users@vger.kernel.org>
Subject: Re: [RELEASE] LTTng-UST 2.12.3 and 2.11.5 (Linux user-space tracer)
Date: Wed, 5 Jan 2022 16:31:05 -0500 (EST) [thread overview]
Message-ID: <739463869.5555.1641418265020.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <697935027.5550.1641418043715.JavaMail.zimbra@efficios.com>
----- On Jan 5, 2022, at 4:27 PM, Mathieu Desnoyers mathieu.desnoyers@efficios.com wrote:
> Hi,
>
> This is a release announcement for the LTTng-UST 2.12.3 and 2.11.5
> tracer. Those are bug fix releases.
>
> The 2.11.5 release marks the end of life (EOL) of the stable-2.11 branch.
> Users experiencing issues with the 2.11 branch are expected to upgrade to
> either 2.12.3 or 2.13.1.
>
> Note that the latest stable branch is 2.13 (its most recent release
> is 2.13.1, released on December 10, 2021).
>
> * Notable changes in 2.12.3:
>
> Two notable fixes are "Fix: nestable pthread cancelstate" and
> "Fix: abort on decrement_sem_count during concurrent tracing start and
> teardown",
> which fix a rare deadlock scenario at application exit.
Just as a clarification, the second fix corrects a race scenario triggering an
assertion failure.
Thanks,
MAthieu
>
> Another notable fix is "fix: liblttng-ust-fd async-signal-safe close()", which
> ensures that the implementation of the symbol interposition for "close" is
> async-signal safe, as it should be.
>
> Please refer to the change logs below for the fixes contained in those
> two releases.
>
> Feedback is welcome,
>
> Thanks,
>
> Mathieu
>
> Project website: https://lttng.org
> Documentation: https://lttng.org/docs
> Download link: https://lttng.org/download
>
>
> 2022-01-05 (National Bird Day) lttng-ust 2.12.3
> * Fix: ust-cancelstate: include string.h for strerror
> * Fix: lttng-ust-fd: remove lttng_ust_common_ctor call
> * Fix: nestable pthread cancelstate
> * Fix: abort on decrement_sem_count during concurrent tracing start and teardown
> * fix: liblttng-ust-fd async-signal-safe close()
> * Set git-review branch to stable-2.12
> * fix: link benchmark with pthread
> * Fix: liblttng-ust-ctl have dependencies on liburcu
> * Fix: add extern "C" to two header files
>
> 2022-01-05 (National Bird Day) lttng-ust 2.11.5
> * Set git-review branch to stable-2.11
> * fix: allow building with userspace-rcu 0.13
>
> --
> Mathieu Desnoyers
> EfficiOS Inc.
> http://www.efficios.com
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2022-01-05 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 21:27 [RELEASE] LTTng-UST 2.12.3 and 2.11.5 (Linux user-space tracer) Mathieu Desnoyers
2022-01-05 21:31 ` Mathieu Desnoyers [this message]
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=739463869.5555.1641418265020.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
/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;
as well as URLs for NNTP newsgroup(s).