From: Mathieu Desnoyers <email@example.com>
Subject: [RELEASE] LTTng-modules 2.13.3 and 2.12.8 (Linux kernel tracer)
Date: Fri, 25 Mar 2022 14:37:32 -0400 (EDT) [thread overview]
Message-ID: <1722467374.194740.1648233452935.JavaMail.firstname.lastname@example.org> (raw)
This is a stable release announcement for the LTTng kernel tracer for the
stable 2.12 and 2.13 branches. The releases are respectively 2.12.8 and 2.13.3.
In the 2.13.3 release, two fixes are worth mentioning:
* Fix: lttng ABI: lttng_counter_ioctl() tainted scalar
The counter aggregate, clear and read functions (used for error reporting of
the event notification feature) use a userspace-controlled "number_dimensions"
argument as loop boundary.
This ABI is only accessible from the root user, which limits the practical impact
of this bug.
* Fix: sample discarded events count before reserve
Sampling the discarded events count in the buffer_end callback is done
out of order, and may therefore include increments performed by following
events (in following packets) if the thread doing the end-of-packet
event write is interrupted for a long time.
Sampling the event discarded counts before reserving space for the last
event in a packet, and keeping this as part of the private ring buffer
context, should fix this race.
In lttng-modules, this scenario would only happen if an interrupt
handler produces many events, when nested over an event between its
reserve and commit. Note that if lttng-modules supports faultable
tracepoints in the future, this may become more easy to trigger due to
This fix is only part of the 2.13 stable branch and not backported to
2.12 because the lib ring buffer code used to implement this fix did not
exist in 2.12. Given that the impact of this bug is only imprecision of
discarded event reporting in corner-case scenarios (small impact, rare
occurrence), the complexity of implementing this fix in 2.12 is not justified.
The effect of this issue is that the lttng-tools
tests/regression/tools/streaming/test_high_throughput_limits test is flaky.
In the 2.12.8 release, a series of commits introduce support for the 5.17 Linux kernel.
The 2.13 stable branch already supported that kernel in the prior releases.
Feedback is welcome!
Project website: https://lttng.org
Download link: https://lttng.org/download
reply other threads:[~2022-03-25 19:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).