Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [RELEASE] LTTng-tools 2.14.2 - Orbitales
Date: Wed, 9 Sep 2026 09:27:43 -0400	[thread overview]
Message-ID: <60f283db-c495-45f9-98f1-7655f9a17695@efficios.com> (raw)

Hi all,

The newest bug-fix release of LTTng-tools 2.14 - Orbitales is now 
available.

2026-09-01 lttng-tools 2.14.3 (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
         * tests: Add `LTTNG_TEST_ABORT_ON_MISSING_PLATFORM_REQUIREMENTS`
         * 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: consumerd: crash when consuming a packet with no output
         * Fix: ust-consumerd: crash when flushing a stream that has no 
chunk
         * 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: 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: 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.14.3.tar.bz2

GPG signature:
https://lttng.org/files/lttng-tools/lttng-tools-2.14.3.tar.bz2.asc

             reply	other threads:[~2026-09-09 13:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 13:27 Kienan Stewart via lttng-dev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-06-05 19:33 Jérémie Galarneau via lttng-dev

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=60f283db-c495-45f9-98f1-7655f9a17695@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=kstewart@efficios.com \
    /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