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.0-rc2 (Linux kernel tracer)
Date: Wed, 14 May 2025 15:53:55 -0400 [thread overview]
Message-ID: <cd6c769f-8d56-475a-b12a-f47426348b95@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 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.
* New in this release
This 2.14.0-rc2 release is a bug fix release in preparation for the
final 2.14 release. The most notable changes are a fix to the
new ring_buffer_flush_or_populate_packet which did not affect x86-64,
but does affect other architecture, causing a snapshot test to fail.
A "nonseekable_open" is introduced to fix python use of the /proc/lttng
file, which affects lttng-modules built against Linux kernels older than
v6.0.
There is an uninitialized variable fix for the experimental CTF2 support,
which only triggers when building against kernels that do not have
CONFIG_INIT_STACK_ALL_ZERO=y, which appears in kernel v5.9.
* Detailed change log:
2025-05-14 LTTng modules 2.14.0-rc2
* Fix channel_backend lookup during `ring_buffer_flush_or_populate_packet`
* Fix: Use `nonseekable_open` for proc files
* Fix: metadata-ctf2: enum mappings are not serialized
Feedback is welcome!
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-05-14 19:54 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=cd6c769f-8d56-475a-b12a-f47426348b95@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