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@lists.lttng.org,
	diamon-discuss@lists.linuxfoundation.org,
	linux-trace-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RELEASE] LTTng-modules 2.14.6 and 2.15.2 (Linux kernel tracer)
Date: Fri, 19 Jun 2026 14:56:17 -0400	[thread overview]
Message-ID: <394956c8-9e78-456b-845d-54a3219214d4@efficios.com> (raw)

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

The LTTng project provides low-overhead, correlated userspace and
kernel tracing on Linux. Its use of the Common Trace Format and a
flexible control interface allows it to fulfill various workloads.

The most relevant changes in these releases introduce support for version
7.1 of the Linux kernel.

* New in these releases:

2026-06-19 LTTng modules 2.15.2
         * fix: leaked file and fd on channel create error
         * fix: backport: hrtimer: Reduce trace noise in hrtimer_start() (v6.1.175)
         * fix: ext4: widen trace event i_ino fields to u64 (v7.1)
         * fix: ext4: delete some unused tracepoint definitions (v5.13)
         * fix: ext4: enhance tracepoints during the folios writeback (v6.17)
         * fix: btrfs: tracepoints, use correct type for inode number (v4.18)
         * fix: vfs: widen trace event i_ino fields to u64 (v7.1)
         * fix: treewide: change inode->i_ino from unsigned long to u64 (v7.1)
         * fix: mm/vmscan: Convert pageout() to take a folio (v5.18)
         * fix: mm: vmscan: add cgroup IDs to vmscan tracepoints (v7.1)
         * fix: hrtimer: Drop unnecessary pointer indirection in hrtimer_expire_entry event (v7.1)
         * fix: hrtimer: Reduce trace noise in hrtimer_start() (v7.1)

2026-06-19 LTTng modules 2.14.6
         * fix: leaked file and fd on channel create error
         * fix: backport: hrtimer: Reduce trace noise in hrtimer_start() (v6.1.175)
         * fix: ext4: widen trace event i_ino fields to u64 (v7.1)
         * fix: ext4: delete some unused tracepoint definitions (v5.13)
         * fix: ext4: enhance tracepoints during the folios writeback (v6.17)
         * fix: btrfs: tracepoints, use correct type for inode number (v4.18)
         * fix: vfs: widen trace event i_ino fields to u64 (v7.1)
         * fix: treewide: change inode->i_ino from unsigned long to u64 (v7.1)
         * fix: mm/vmscan: Convert pageout() to take a folio (v5.18)
         * fix: mm: vmscan: add cgroup IDs to vmscan tracepoints (v7.1)
         * fix: hrtimer: Drop unnecessary pointer indirection in hrtimer_expire_entry event (v7.1)
         * fix: hrtimer: Reduce trace noise in hrtimer_start() (v7.1)

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

Enjoy!

Mathieu

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


                 reply	other threads:[~2026-06-19 18:56 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=394956c8-9e78-456b-845d-54a3219214d4@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