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-UST 2.14.3 (EOL) and 2.15.2 (Linux user-space tracer)
Date: Tue, 8 Sep 2026 15:50:32 -0400 [thread overview]
Message-ID: <9e5ca6e9-1b5e-40c7-b38a-1a47ac3d9198@efficios.com> (raw)
LTTng-UST, the Linux Trace Toolkit Next Generation Userspace Tracer,
is a low-overhead application tracer. The library "liblttng-ust" enables
tracing of applications and libraries.
The most relevant bug fix can be found in the 2.15.2 release. It adds
bounded retry loops for per-channel buffers, thus fixing a regression
affecting the supported event throughput. This regression was introduced
by the robust ring buffers in LTTng-UST 2.15 and affected specifically
the per-channel buffers.
Note that version 2.14.3 of LTTng-UST is the last version of that stable
branch. With this release, the 2.14 branch of LTTng-UST has now reached
its cycle "End of Life".
Please upgrade to 2.15.x or 2.16.x if you wish to benefit from new
features and future bug fixes.
* New in these releases:
2026-09-08 lttng-ust 2.15.2
* tests: Disable coredumps for expected ABI failures
* Fix: lttng_ust_build_bug_on undefined behavior in C++ builds
* Fix: ringbuffer: retry on wrap-around contention for per-channel buffers
* Fix: Introduce concurrent subbuffer-ownership retry loop
* lttng-ust(3): document lttng_ust_field_unused()
* lttng-ust(3): document LTTNG_UST_TRACEPOINT_MODEL_EMF_URI()
2026-09-08 lttng-ust 2.14.3
* tests: Disable coredumps for expected ABI failures
* Fix: lttng_ust_build_bug_on undefined behavior in C++ builds
* lttng-ust(3): document lttng_ust_field_unused()
* lttng-ust(3): document LTTNG_UST_TRACEPOINT_MODEL_EMF_URI()
Project website: https://lttng.org
Documentation: https://lttng.org/docs
Download link: https://lttng.org/download
Enjoy!
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
reply other threads:[~2026-09-08 19:50 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=9e5ca6e9-1b5e-40c7-b38a-1a47ac3d9198@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