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: [lttng-dev] [RELEASE] LTTng-modules 2.13.14 and 2.12.18 (Linux kernel tracer)
Date: Thu, 18 Jul 2024 13:44:04 -0400 [thread overview]
Message-ID: <1b61d65c-6c0e-4312-9939-cfdd3fd627ac@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 highlight of these releases is the added support for Linux v6.10
in LTTng-modules v2.13.14.
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 these releases:
* LTTng-modules 2.13.14:
- Introduce support for Linux v6.10.
- Fix build on CentOS 9 Stream 2024-6.
- Fix mm_vmscan_lru_isolate tracepoint build against RHEL 9.4 kernels
* In both LTTng-modules 2.12.18 and 2.13.14:
- Fix kvm_mmio event NULL pointer dereference in KVM instrumentation.
This is triggered in case of unsatisfied MMIO read.
- Fix fdtable wrapper (lttng_lookup_fd_rcu()) for kernel ranges
5.10.220+.
As usual feedback is welcome!
Project website: https://lttng.org
Documentation: https://lttng.org/docs
Download link: https://lttng.org/download
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
reply other threads:[~2024-07-18 17:44 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=1b61d65c-6c0e-4312-9939-cfdd3fd627ac@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