From: "Jérémie Galarneau" <jeremie.galarneau@efficios.com>
To: lttng-dev <lttng-dev@lists.lttng.org>
Cc: diamon-discuss <diamon-discuss@lists.linuxfoundation.org>,
linux-trace-users <linux-trace-users@vger.kernel.org>
Subject: [RELEASE] LTTng-tools 2.11.8 - Lafontaine
Date: Tue, 19 Oct 2021 17:13:29 -0400 (EDT) [thread overview]
Message-ID: <1790858757.21395.1634678009452.JavaMail.zimbra@efficios.com> (raw)
Hi all,
We have just released the eighth and final bug-fix release of LTTng-tools 2.11 -
Lafontaine. This release addresses the issues listed below.
2021-10-18 lttng-tools 2.11.8 (National Chocolate Cupcake Day)
* Fix: sessiond: previously created channel cannot be enabled
* Fix: ust: app stuck on recv message during UST comm timeout scenario
* Fix: ust: UST communication can return -EAGAIN
* Fix: ust: segfault on lttng start on filter bytecode copy
* Build fix: Missing message in LTTNG_DEPRECATED invocation
* include: remove spurious spaces in condition/session-rotation.h
* fix: wrong define used for GCC version check
* Fix: userspace-probe: unreported error on string copy error
* Fix: userspace-probe: truncating binary path for SDT
* Fix: sessiond: ust session is inactive during ust_app_global_update
* Fix: man: lttng-rotate: trace file count/size limitation does not apply
* Fix: rotation client example: leak of handle on error
* Fix: use of uninitialised bytes valgrind warning
* Fix: bump minimal urcu dependency to 0.11
* Fix: list_lttng_agent_events: unbalanced RCU read-side lock on error
* Fix: consumer: unbalanced RCU read-side lock on error
As always, please report any issue you may encounter to bugs.lttng.org
or on this mailing list.
Project website: https://lttng.org
Download link:
https://lttng.org/files/lttng-tools/lttng-tools-2.11.8.tar.bz2
GPG signature:
https://lttng.org/files/lttng-tools/lttng-tools-2.11.8.tar.bz2.asc
reply other threads:[~2021-10-19 21:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1790858757.21395.1634678009452.JavaMail.zimbra@efficios.com \
--to=jeremie.galarneau@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).