From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev@lists.lttng.org,
diamon-discuss@lists.linuxfoundation.org,
linux-trace-users@vger.kernel.org, lwn@lwn.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [RELEASE] LTTng-modules 2.12.0-rc2, 2.11.2, 2.10.14 (Linux kernel tracer)
Date: Tue, 25 Feb 2020 15:38:45 -0500 (EST) [thread overview]
Message-ID: <1487536566.7003.1582663125006.JavaMail.zimbra@efficios.com> (raw)
Hi,
This release announcement covers all actively maintained branches of the
LTTng-modules Linux kernel tracer, namely:
- LTTng-modules 2.10.14 and 2.11.2 (stable branches),
- LTTng-modules 2.12.0-rc2 (branch currently in release candidate cycle).
The LTTng modules provide Linux kernel tracing capability to the LTTng
tracer toolset.
* New and noteworthy in these releases:
- Support for kernel 5.6 (currently at 5.6-rc3). It features changes in the
tracepoint instrumentation, and changes in the timekeeping area in
preparation for y2038. The plan here to handle timekeeping changes
and keep backward compatibility is to add forward declarations of
deprecated types locally in lttng-modules for the stable branches.
For the master branch and future 2.13+ releases, we plan to introduce a
type compatibility layer within lttng-modules with typedefs mapping to the
new types when building against recent kernels, and provide backward
compatible typedefs when building against older kernels. Currently,
lttng-modules builds against all vanilla and most distribution Linux
kernels from v3.0 onwards.
- Fix NULL pointer dereference race in the lttng-statedump module. The
return value of task_active_pid_ns() should be checked for NULL to handle
tasks which have exited but were not waited-for yet, which are thus in a
"dead" state. The statedump triggers at trace start and when the command
"lttng regenerate statedump" is issued.
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-02-25 20:38 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=1487536566.7003.1582663125006.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
--cc=lwn@lwn.net \
/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).