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: [diamon-discuss] [RELEASE] LTTng-modules 2.9.11, 2.10.8, 2.11.0-rc2 (Linux kernel tracer)
Date: Thu, 1 Nov 2018 18:56:22 -0400 (EDT) [thread overview]
Message-ID: <60988959.4070.1541112982406.JavaMail.zimbra@efficios.com> (raw)
Hi,
This is a set of bugfix releases of the LTTng modules kernel tracer.
It covers the three currently active lttng-modules branches: the
2.9 and 2.10 stable branches, as well as the 2.11 branch in release
candidate cycle.
Those releases add support for kernel 4.19.
One important improvement is to prevent allocation of buffers larger
than the available memory, which can cause the OOM killer to trigger.
Even if the OOM killer end up having to trigger, the current OOM kill
target is set to the current thread while allocating buffers.
Enjoy!
Mathieu
Project website: http://lttng.org
Documentation: http://lttng.org/docs
Download link: http://lttng.org/download
Changelog:
2018-11-01 (National Men Make Dinner Day) LTTng modules 2.11.0-rc2
* Fix: update kvm instrumentation for SLES12 SP2 LTSS >= 4.4.121-92.92
* Fix: Add missing const to lttng_tracepoint_ptr_deref prototype
* Fix: adapt to kernel relative references
* Fix: implicit declarations caused by buffer size checks.
* Prevent allocation of buffers if exceeding available memory
* Fix: btrfs instrumentation namespacing
* Fix: Convert rcu tracepointis to gp_seq (v4.19)
* Fix: tracing: Centralize preemptirq tracepoints (4.19)
* Fix: net: expose sk wmem in sock_exceed_buf_limit tracepoint (4.19)
* Fix: access migrate_disable field directly
* Fix: out of memory error handling
2018-11-01 (National Men Make Dinner Day) LTTng modules 2.10.8
* Fix: update kvm instrumentation for SLES12 SP2 LTSS >= 4.4.121-92.92
* Fix: Add missing const to lttng_tracepoint_ptr_deref prototype
* Fix: adapt to kernel relative references
* Fix: implicit declarations caused by buffer size checks.
* Prevent allocation of buffers if exceeding available memory
* Fix: Convert rcu tracepointis to gp_seq (v4.19)
* Fix: net: expose sk wmem in sock_exceed_buf_limit tracepoint (4.19)
* Fix: access migrate_disable field directly
* Fix: out of memory error handling
2018-11-01 (National Men Make Dinner Day) LTTng modules 2.9.11
* Fix: update kvm instrumentation for SLES12 SP2 LTSS >= 4.4.121-92.92
* Fix: Add missing const to lttng_tracepoint_ptr_deref prototype
* Fix: adapt to kernel relative references
* Fix: implicit declarations caused by buffer size checks.
* Prevent allocation of buffers if exceeding available memory
* Fix: Convert rcu tracepointis to gp_seq (v4.19)
* Fix: net: expose sk wmem in sock_exceed_buf_limit tracepoint (4.19)
* Fix: access migrate_disable field directly
* Fix: out of memory error handling
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next reply other threads:[~2018-11-01 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 22:56 Mathieu Desnoyers [this message]
2018-11-01 23:33 ` [diamon-discuss] [RELEASE] LTTng-modules 2.9.11, 2.10.8, 2.11.0-rc2 (Linux kernel tracer) Joel Fernandes
2019-03-19 17:34 ` Mathieu Desnoyers
2019-03-21 12:41 ` Joel Fernandes
2019-03-21 13:13 ` Steven Rostedt
2019-03-22 13:48 ` Joel Fernandes
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=60988959.4070.1541112982406.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