From: "Jérémie Galarneau" <jeremie.galarneau@efficios.com>
To: 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.12.7 - (Ta) Meilleure
Date: Fri, 17 Dec 2021 14:03:05 -0500 [thread overview]
Message-ID: <Ybze6ZpA95wGqjUv@carbonara> (raw)
Hi all,
We have just released the seventh bug-fix release of LTTng-tools 2.12 - (Ta)
Meilleure. This release addresses a number of issues listed below.
2021-12-17 lttng-tools 2.12.7 (National Ugly Christmas Sweater Day)
* Validate channel context mismatch across UST applications
* Fix: relayd: compare viewer chunks by ID rather than address
* Fix: relayd: live: erroneous message timestamp observed from live viewer
* Fix: relayd comm: improperly packed rotate streams command header
* test: snapshot after regenerate metadata
* Fix: ust-consumer: segfault on snapshot after regenerate metadata
* Tests: live kernel: no plan printed when non-root
* Fix: sessiond: snapshot: leak of trace chunk
* Fix: test: use BABELTRACE_BIN instead of babeltrace
* Fix: relayd: `!vsession->current_trace_chunk` assertion failed
* Fix: tests: fix unused-but-set warning in test_fd_tracker.c
* Fix: sessiond: fix possible buffer overflow warning
* Fix: lttng-ctl: tracing_group memory leaks
* Fix: Tests: unchecked `close()` return value
* Fix: relayd: live: mishandled initial null trace chunk
* Fix: configure.ac: reporting SDT uprobe as a UST feature
* Fix: Tests: leaking epoll fd
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.12.7.tar.bz2
GPG signature:
https://lttng.org/files/lttng-tools/lttng-tools-2.12.7.tar.bz2.asc
reply other threads:[~2021-12-17 19:03 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=Ybze6ZpA95wGqjUv@carbonara \
--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).