Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>,
	Diamon discuss <diamon-discuss@lists.linuxfoundation.org>,
	linux-trace-users <linux-trace-users@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [RELEASE] LTTng-modules 2.15.3 and 2.14.7 (Linux kernel tracer)
Date: Mon, 17 Aug 2026 10:50:52 -0400	[thread overview]
Message-ID: <72b01b28-75ac-43d5-85b8-2a9317c946c3@efficios.com> (raw)

Hi,

This is a stable release announcement for the LTTng kernel tracer,
an out-of-tree kernel tracer for the Linux kernel.

* Highlights

LTTng-modules 2.15.3 adds support for the Linux kernel v7.2.
The 2.14.x releases of LTTng-modules now have an upper bound:
they support kernels up to v7.1. Considering that we expect
LTTng-modules 2.16.0 final to be released around next week,
we can expect this 2.14.7 release to be the last one for the
stable-2.14 branch.

A fix appears in those releases: since we introduced the
"flush or populate packet ioctl", a kernel trace could contain
zeroed UUID in the very last packet of the streams within snapshots,
thus causing Babeltrace 2 to fail with e.g.:

         Invalid metadata stream UUID:
         uuid=00000000-0000-0000-0000-000000000000,
         expected-uuid=8962f7e1-f875-8f47-a112-43868a4b000b

The commit "Fix: ring buffer: zeroed UUID in populated empty packet headers"
fixes this issue.

* New in these releases:

2026-08-17 LTTng modules 2.15.3
         * fix: backport: hrtimer: Reduce trace noise in hrtimer_start() (Ubuntu-6.8.0-136)
         * fix: string: Remove strncpy() from the kernel (v7.2)
         * fix: btrfs: tracepoints: trace transaction states during commit phase (v7.2)
         * fix: btrfs: tracepoints: add in_fsync field to transaction commit event (v7.2)
         * fix: btrfs: tracepoints: pass a transaction handle to transaction commit event (v7.2)
         * fix: net: constify sk_skb_reason_drop() sock parameter (v7.2)
         * fix: KVM: x86: Rename kvm_cache_regs.h => regs.h (v7.2)
         * fix: x86/msr: Remove rdmsrl() / wrmsrl() (v7.2)
         * fix: warning -Wordered-compare-function-pointers with LLVM
         * fix: warning -Wcast-function-type-strict with LLVM
         * Fix: ring buffer: zeroed UUID in populated empty packet headers

2026-08-17 LTTng modules 2.14.7
         * Document last supported kernel version for stable-2.14 branch
         * fix: backport: hrtimer: Reduce trace noise in hrtimer_start() (Ubuntu-6.8.0-136)
         * fix: warning -Wordered-compare-function-pointers with LLVM
         * fix: warning -Wcast-function-type-strict with LLVM
         * Fix: ring buffer: zeroed UUID in populated empty packet headers

Project website: https://lttng.org
Documentation: https://lttng.org/docs
Download link: https://lttng.org/download

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com


                 reply	other threads:[~2026-08-17 14:51 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=72b01b28-75ac-43d5-85b8-2a9317c946c3@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-users@vger.kernel.org \
    --cc=mathieu.desnoyers@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