From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
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.13.22 and 2.14.3 (Linux kernel tracer)
Date: Fri, 17 Oct 2025 12:08:27 -0400 [thread overview]
Message-ID: <52d5784e-cb07-4519-9c13-d7585bd5a9e7@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.
The main change included in both 2.13.22 and 2.14.3 releases is a fix for the
get_pfnblock_flags_mask / get_pfnblock_migratetype wrappers for v6.17.
It adds a version gate for the get_pfnblock_flags_mask wrapper as the
symbol was removed in v6.17 and thus initialization would always fail
preventing the modules load.
The fix of CTF version in metadata packet headers for CTF2 should not
have observable effects for end users, it's mostly for consistency.
* Changelog:
2025-10-17 LTTng modules 2.13.22
* fix: always print to kernel log on module load failure
* fix: get_pfnblock_flags_mask / get_pfnblock_migratetype wrappers for v6.17
2025-10-17 LTTng modules 2.14.3
* Fix: Set CTF version in metadata packet headers for CTF2
* fix: always print to kernel log on module load failure
* fix: get_pfnblock_flags_mask / get_pfnblock_migratetype wrappers for v6.17
* fix: remove duplicated MODULE macros
Thanks,
Mathieu
Project website: https://lttng.org
Documentation: https://lttng.org/docs
Download link: https://lttng.org/download
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
reply other threads:[~2025-10-17 16:08 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=52d5784e-cb07-4519-9c13-d7585bd5a9e7@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=lttng-dev@lists.lttng.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