From: "Jérémie Galarneau via lttng-dev" <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Cc: diamon-discuss@lists.linuxfoundation.org,
linux-trace-users@vger.kernel.org
Subject: [RELEASE] LTTng-tools 2.13.15 - Nordicité
Date: Mon, 14 Apr 2025 14:50:32 -0400 [thread overview]
Message-ID: <Z_1Y-Arx-nSh5wDY@efficios.com> (raw)
Hi all,
We have just released the fifteenth bug-fix release of LTTng-tools 2.13 -
Nordicité. This release addresses a number of issues listed below.
2025-04-11 lttng-tools 2.13.15 (National Poutine Day)
* Fix: build with urcu 0.15 on 32bit archs with 64bit time_t
* Tests: Make notifier discard count test more robust
* Fix: Update lttng-modules load list
* Fix: sessiond: notification-thread: add to pollset fails silently
* Fix: path: handle truncation in utils_partial_realpath()
* Fix: path: handle truncation in utils_partial_realpath()
* Fix: sessiond: assertion on inconsistent filter bytecode and expression
* Fix: uprobe event-rule: logging mentions pattern instead of name
* Fix: relayd: leaked socket for live connections
* Fix: unload all kernel modules on sessiond exit
* lttng: Warn on session start when client-visible shm path is too small
* lttng-ctl/lttng: Move enable-channel memory check to client
* lttng-ctl: Use max possible CPUs for per-CPU memory estimation
* common: Add helper to get max possible CPU count
* lttng-ctl: Mark random seed helpers as hidden
* lttng-ctl: Mark notification-internal symbols as hidden
* Fix: sessiond: size-based kernel rotation doesn't trigger
* Fix: Close per-process event notifier error accounting fds on registration
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.13.15.tar.bz2
GPG signature:
https://lttng.org/files/lttng-tools/lttng-tools-2.13.15.tar.bz2.asc
reply other threads:[~2025-04-14 18:50 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=Z_1Y-Arx-nSh5wDY@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=jeremie.galarneau@efficios.com \
--cc=linux-trace-users@vger.kernel.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