From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev@lists.lttng.org,
diamon-discuss@lists.linuxfoundation.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [RELEASE] LTTng modules 2.10.0-rc2, 2.9.3, 2.8.6
Date: Mon, 12 Jun 2017 22:06:22 +0000 (UTC) [thread overview]
Message-ID: <800720578.11295.1497305182681.JavaMail.zimbra@efficios.com> (raw)
The LTTng modules provide Linux kernel tracing capability to the LTTng
tracer toolset.
Those versions are bugfixes in the currently maintained stable
branches of lttng-modules. They mainly contain:
- Fix for the "PID tracker" feature, which should track pgid, which
corresponds to the notion of process ID in user-space. It is now
in sync with the feature in the UST tracing domain (application
tracing),
- Adding a "flush empty" ioctl for snapshots fixes cases where the
Babeltrace lttng-live reader has issues keeping up with a steady
stream of useless empty packets. This "flush empty" ioctl is
introduced in backwards and forwards compatible ways, to ensure
smooth upgrade within the stable versions of lttng-tools and
lttng-modules.
Those releases also add support for 4.12 release candidate kernels.
Enjoy!
Mathieu
Project website: http://lttng.org
Documentation: http://lttng.org/docs
Download link: http://lttng.org/download
Detailed change logs:
2017-06-12 (National Peanut Butter Cookie Day) LTTng modules 2.10.0-rc2
* Fix: pid tracker should track "pgid"
* Fix: Build ftrace probe on kernels prior to 4.12
* Fix: update ftrace probe for kernel 4.12
* Fix: update block instrumentation for kernel 4.12
* Fix: Add support for 4.9.27-rt18 kernel
* Fix: update btrfs instrumentation for kernel 4.12
* Fix: update ringbuffer for kernel 4.12
* Fix: update sched instrumentation for kernel 4.12
* Fix: ext3 was completely removed from the kernel in v4.3
* Fix: NULL pointer dereference of THIS_MODULE with built-in modules
* Fix: add "flush empty" ioctl for stream intersection
* Revert "Fix: flush empty packets on snapshot channel"
* Revert "Fix: don't perform extra flush on metadata channel"
2017-06-12 (National Peanut Butter Cookie Day) LTTng modules 2.9.3
* Fix: pid tracker should track "pgid"
* Fix: Build ftrace probe on kernels prior to 4.12
* Fix: update ftrace probe for kernel 4.12
* Fix: update block instrumentation for kernel 4.12
* Fix: Add support for 4.9.27-rt18 kernel
* Fix: update btrfs instrumentation for kernel 4.12
* Fix: update ringbuffer for kernel 4.12
* Fix: update sched instrumentation for kernel 4.12
* Fix: ext3 was completely removed from the kernel in v4.3
* Fix: NULL pointer dereference of THIS_MODULE with built-in modules
* Fix: add "flush empty" ioctl for stream intersection
* Revert "Fix: flush empty packets on snapshot channel"
* Revert "Fix: don't perform extra flush on metadata channel"
* Fix: remove CONFIG_KALLSYMS_ALL warning on clean
2017-06-12 (National Peanut Butter Cookie Day) LTTng modules 2.8.6
* Fix: pid tracker should track "pgid"
* Fix: Build ftrace probe on kernels prior to 4.12
* Fix: update ftrace probe for kernel 4.12
* Fix: update block instrumentation for kernel 4.12
* Fix: Add support for 4.9.27-rt18 kernel
* Fix: update btrfs instrumentation for kernel 4.12
* Fix: update ringbuffer for kernel 4.12
* Fix: update sched instrumentation for kernel 4.12
* Fix: ext3 was completely removed from the kernel in v4.3
* Fix: NULL pointer dereference of THIS_MODULE with built-in modules
* Fix: add "flush empty" ioctl for stream intersection
* Revert "Fix: flush empty packets on snapshot channel"
* Revert "Fix: don't perform extra flush on metadata channel"
* Fix: remove CONFIG_KALLSYMS_ALL warning on clean
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
reply other threads:[~2017-06-12 22:10 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=800720578.11295.1497305182681.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@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