linux-trace-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev@lists.lttng.org,
	diamon-discuss@lists.linuxfoundation.org,
	linux-trace-users@vger.kernel.org
Subject: [RELEASE] LTTng-UST 2.10.7, 2.11.1, 2.12.0-rc2 (Linux user-space tracer)
Date: Wed, 4 Mar 2020 16:27:08 -0500 (EST)	[thread overview]
Message-ID: <1372342050.18535.1583357228871.JavaMail.zimbra@efficios.com> (raw)

Hi,

This announcement covers new releases in the two actively maintained
stable branches of the LTTng-UST project (2.10.7 and 2.11.1), as well as
the second release candidate for the 2.12 branch (2.12.0-rc2).

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.

* Noteworthy fixes:

All of these releases contain a fix which ensures the FD_CLOEXEC flag
is set for _all_ file descriptors received by lttng-ust over unix
socket. This fixes an issue where more file descriptors than expected
stay open over exec.

Fixes were introduced to please the address sanitizer (ASan) part of
clang-9. One documented out-of-bound access was done by jhash as an
"optimization" which was rightfully tripping ASan. Since this is
not a fast-path, the optimization was removed and we always use the
slower "valgrind-safe" code path. We also annotated the variables
emitted in the __tracepoints_ptrs to ensure ASan does not emit
redzones around those variables, which are means to be contiguous
within the section.

For the 2.10 and 2.11 branches, building with -fno-common is
enforced to prepare for the upcoming default behavior change
in gcc 10.

Please try it out, and as usual, feedback is welcome!

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

                 reply	other threads:[~2020-03-04 21:27 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=1372342050.18535.1583357228871.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    --cc=linux-trace-users@vger.kernel.org \
    --cc=lttng-dev@lists.lttng.org \
    /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).