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.13.17 (Linux kernel tracer)
Date: Fri, 24 Jan 2025 15:54:55 -0500 [thread overview]
Message-ID: <6c4edb5a-5506-4cb4-a251-ed77fcb385ae@efficios.com> (raw)
Hi,
This is a stable release announcement for the LTTng kernel tracer,
a kernel tracer for the Linux kernel.
The most relevant news about this release is added support for
the Linux kernel v6.13 and for the RHEL 9.5 kernels by LTTng-modules
v2.13.17.
We are aware that this release of LTTng-modules fails to build
against sles15sp5 and Linux v6.13 on powerpc32 in our CI. We will
investigate and fix these in a future release, but we aim to release
promptly after Linux v6.13, so considering that LTTng-modules 2.13.x
has never successfully built against those kernels, those are not
considered release blockers.
Detailed change log:
2025-01-24 (Global Belly Laugh Day) LTTng modules 2.13.17
* fix: include linux/fs.h for 'struct file' definition (v4.5)
* fix: add missing check for __must_check 'lttng_file_ref_put()' (v6.13)
* Fix: uprobe consumer handler signature changed in Linux 6.13.0-rc1
* Fix: lookup_fdget_rcu removed in Linux 6.13.0-rc1
* Fix: f_count replaced with f_ref in Linux 6.13.0-rc1
* Fix: sched_stat_runtime changed in Linux 6.6.66
* lttng-modules fix for RHEL 9.5 kernels
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-01-24 20:55 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=6c4edb5a-5506-4cb4-a251-ed77fcb385ae@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