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.13.21 and 2.14.2 (Linux kernel tracer)
Date: Mon, 6 Oct 2025 11:50:55 -0400 [thread overview]
Message-ID: <3ca8430a-d2c1-4fc4-8fa7-bc3fa53ee82e@efficios.com> (raw)
Hi,
Those LTTng-modules stable releases mainly fix an missing preemption off
issue with system call instrumentation when using LTTng-modules against
a Linux kernel v6.13 or more recent, with preemptible kernels (PREEMPT
or PREEMPT_LAZY configurations). Users of LTTng-modules with those
configurations should upgrade.
This issue is the result of an upstream kernel change (introduction of
faultable syscall tracepoints), without the introduction of the
corresponding changes in LTTng-modules.
One effect of this bug is corruption of per-cpu linked-lists under
load. It also possible that the ring buffer corrupts itself because
of unexpected producer migration.
The other change in those releases is the introduction of a wrapper for
`get_pfnblock_migatetype` to build against v6.17 kernels.
* New in this release:
2025-10-06 LTTng modules 2.14.2
* Fix: Add wrapper for `get_pfnblock_migatetype`
* Fix: Protect syscall probes with preemption disable
2025-10-06 LTTng modules 2.13.21
* Fix: Add wrapper for `get_pfnblock_migatetype`
* Fix: Protect syscall probes with preemption disable
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-06 15:51 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=3ca8430a-d2c1-4fc4-8fa7-bc3fa53ee82e@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;
as well as URLs for NNTP newsgroup(s).