From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Cc: linux-trace-users@vger.kernel.org,
diamon-discuss@lists.linuxfoundation.org
Subject: [RELEASE] LTTng-tools 2.15.2 - Péché Mortel
Date: Wed, 9 Sep 2026 09:29:29 -0400 [thread overview]
Message-ID: <ecb20671-5c82-4d00-a6d5-45c8badce8a8@efficios.com> (raw)
Hi all,
The newest bug-fix release of LTTng-tools 2.15 - Péché Mortel is now
available.
2026-09-01 lttng-tools 2.15.2 (Ginger Cat Appreciation Day)
* tests: Use version-appropriate GDB logging command
* sessiond: Allow missing UST app channel when modifying events
* tests: Add regression test for sessiond assert
* tests: Backport `disable_recording_rule`
* tests: Backport `possible_cpus_array_len`
* tests: Backport consumerd pid fetching
* tests: Add debug option to GDB scripts for automatic print
statements
* tests: Add option to limit the number of tests skipped for
missing requirements
* tests: Add helper to fetch logging formatter
* tests: Add GDB helpers to lttngtest.utils
* Replace removed Python 2 C API macros for SWIG 4.5.0
compatibility
* Fix: ust-consumerd: oldest packet lost in snapshot of active
channel
* Fix: common: check load data type in filter globbing validation
* Fix: common: bound filter IR nesting depth
* Fix: sessiond: validate filter bytecode generation length
* Fix: common: harden trigger-list header decoding against
short payloads
* Fix: common: validate action header length before dereferencing
* Fix: common: daemon abort on invalid log-level-rule type
* Fix: common: validate action list payload length
* Fix: sessiond: sanitize agent event-listing reply
* Fix: common: sanitize event exclusion count on deserialization
* Fix: consumerd: crash when consuming a packet with no output
* Fix: ust-consumerd: crash when flushing a stream that has no
chunk
* Fix: consumerd: no packet produced for idle streams on rotation
* Fix: ust-consumerd: reclaim timer resumed for a single
channel only
* Fix: ust-consumerd: crash on deferred reclaim without an age
limit
* Fix: ust-consumerd: reclaim timer not resumed after explicit
reclaim
* common: re-arm a cancelled scheduler task when it is rescheduled
* Fix: ust-consumerd: lock inversion between reclaim request
and scheduler
* Fix: tests: lttngtest: taskset_anycpu() retries the same CPU
forever
* Fix: relayd: 32-bit overflow of packet total size
* Fix: relayd: NULL file handle dereference in GET_PACKET
* Fix: relayd: live viewer can reach unattached sessions
* Fix: relayd: size overflow in the live viewer GET_PACKET command
* Fix: relayd: reject zero tracefile count
* Fix: tests: stall-buffer timer relies on a packet-count artifact
* Fix: ust-consumerd: stall watchdog ignores snapshot channels
* Fix: relayd: incomplete session base path validation
* Fix: relayd: stream channel name allows path traversal
* Fix: relayd: stream path traversal via reversed strstr() check
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.15.2.tar.bz2
GPG signature:
https://lttng.org/files/lttng-tools/lttng-tools-2.15.2.tar.bz2.asc
reply other threads:[~2026-09-09 13:30 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=ecb20671-5c82-4d00-a6d5-45c8badce8a8@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=kstewart@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