From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: Diamon discuss <diamon-discuss@lists.linuxfoundation.org>,
lttng-dev <lttng-dev@lists.lttng.org>,
linux-trace-users <linux-trace-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [lttng-dev] [RELEASE] LTTng-UST 2.13.3 and 2.12.5 (Linux user-space tracer)
Date: Fri, 3 Jun 2022 16:09:08 -0400 (EDT) [thread overview]
Message-ID: <2013849140.21031.1654286948952.JavaMail.zimbra@efficios.com> (raw)
Hi,
This is a stable release announcement for the LTTng-UST project. LTTng-UST
is a tracer for Linux user-space applications. The respective versions are
2.13.3 and 2.12.5.
Those are bug fix releases correcting a few issues in both stable branches,
namely by removing use of non-async-signal-safe functions in the ERR()
error-printing macros, and fixing a use-after-free memory read in a list
traversal within the statedump code.
Specifically in 2.13.3, the bytecode interpreter in LTTng-UST left the
context fields byte order uninitialized, thus leading to bogus context field
values in the event notification capture feature. Fix this by initializing
the byte order.
Also specifically in 2.13.3, a too-strict validation of array/sequence field
types is relaxed to allow pointer types to be used as integer values. This
was allowed prior to 2.13, and this too-strict validation was therefore an
instrumentation API regression.
Detailed Changelog:
2022-06-03 (National Repeat Day) (National Repeat Day) lttng-ust 2.13.3
* Document ust lock async-signal-safety
* Fix: don't use strerror() from ust lock nocheck
* Fix: remove non-async-signal-safe fflush from ERR()
* Fix: Pointers are rejected by integer element compile time assertion for array and sequence
* Fix: statedump: invalid read during iter_end
* Fix: bytecode interpreter context_get_index() leaves byte order uninitialized
2022-06-03 (National Repeat Day) (National Repeat Day) lttng-ust 2.12.5
* Document ust lock async-signal-safety
* Fix: don't use strerror() from ust lock nocheck
* Fix: remove non-async-signal-safe fflush from ERR()
* Fix: statedump: invalid read during iter_end
* Fix: bytecode interpreter context_get_index() leaves byte order uninitialized
Thanks,
Mathieu
Project website: https://lttng.org
Documentation: https://lttng.org/docs
Download link: https://lttng.org/download
--
Mathieu Desnoyers
EfficiOS Inc.
http://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:[~2022-06-03 20:09 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=2013849140.21031.1654286948952.JavaMail.zimbra@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 read-only IMAP folder(s) and NNTP newsgroup(s).