From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev@lists.lttng.org, diamon-discuss@lists.linuxfoundation.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [RELEASE] LTTng-modules 2.9.8 and 2.10.5 (Linux kernel tracer)
Date: Tue, 30 Jan 2018 21:02:17 +0000 (UTC) [thread overview]
Message-ID: <1016989198.12891.1517346137739.JavaMail.zimbra@efficios.com> (raw)
The stable releases 2.9.8 and 2.10.5 of the LTTng-modules kernel tracer
introduces support for the 4.15 Linux kernel, updates support for currently
maintained Linux kernel stable branches, and contains bugfixes.
The LTTng modules provide Linux kernel tracing capability to the LTTng
tracer toolset.
Project website: http://lttng.org
Documentation: http://lttng.org/docs
Download link: http://lttng.org/download
Changelog:
2018-01-30 (National Croissant Day) LTTng modules 2.9.8
* Fix: network instrumentation protocol enum
* Fix: update btrfs instrumentation for SuSE 4.4.103-6
* Fix: update block instrumentation for SuSE 4.4.73-5
* Fix: global_dirty_limit for kernel v4.2 and up
* Fix: network instrumentation handling of corrupted TCP headers
* Fix: add missing uaccess.h include from kstrtox.h wrapper
* Update: kvm instrumentation for 4.14.14+, 4.9.77+, 4.4.112+
* Fix: btrfs_delayed_ref_head was unwired since v3.12
* Update kvm instrumentation for debian kernel 4.9.65-3
* Fix: debian kernel version parsing
* Fix: block instrumentation 4.14+ NULL pointer dereference
* Update: kvm instrumentation for 3.16.52 and 3.2.97
* Fix: kvm instrumentation for 4.15
* Update sock instrumentation for 4.15
* Update kvm instrumentation for 4.15
* Fix: ACCESS_ONCE() removed in kernel 4.15
* Fix: sched instrumentation on stable RT kernels
* timer API transition for kernel 4.15
* Fix: Don't nest get online cpus
* Fix: lttng_channel_syscall_mask() bool use in bitfield
* Fix: update kmem instrumentation for kernel 4.15
2018-01-30 (National Croissant Day) LTTng modules 2.10.5
* Fix: network instrumentation protocol enum
* Fix: update btrfs instrumentation for SuSE 4.4.103-6
* Fix: update block instrumentation for SuSE 4.4.73-5
* Fix: global_dirty_limit for kernel v4.2 and up
* Fix: network instrumentation handling of corrupted TCP headers
* Fix: add missing uaccess.h include from kstrtox.h wrapper
* Update: kvm instrumentation for 4.14.14+, 4.9.77+, 4.4.112+
* Fix: btrfs_delayed_ref_head was unwired since v3.12
* Update kvm instrumentation for debian kernel 4.9.65-3
* Fix: debian kernel version parsing
* Fix: block instrumentation 4.14+ NULL pointer dereference
* Update: kvm instrumentation for 3.16.52 and 3.2.97
* Fix: kvm instrumentation for 4.15
* Update sock instrumentation for 4.15
* Update kvm instrumentation for 4.15
* Fix: ACCESS_ONCE() removed in kernel 4.15
* Fix: sched instrumentation on stable RT kernels
* timer API transition for kernel 4.15
* Fix: Don't nest get online cpus
* Fix: lttng_channel_syscall_mask() bool use in bitfield
* Fix: update kmem instrumentation for kernel 4.15
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
reply other threads:[~2018-01-30 21:01 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=1016989198.12891.1517346137739.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
Powered by JetHome