From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>,
Diamon discuss <diamon-discuss@lists.linuxfoundation.org>,
linux-trace-users <linux-trace-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [lttng-dev] [RELEASE] LTTng-modules 2.13.4 and 2.12.9 (Linux kernel tracer)
Date: Fri, 3 Jun 2022 15:30:35 -0400 (EDT) [thread overview]
Message-ID: <846400291.20840.1654284635213.JavaMail.zimbra@efficios.com> (raw)
Hi,
The 2.13.4 and 2.12.9 releases are bug fix releases for the currently
maintained LTTng-modules stable branches.
Noteworthy in the 2.12.9 release:
The README.md file now document that the stable-2.12 branch of
LTTng-modules supports Linux kernels between 3.0 and 5.17 (inclusive).
Support for the 5.18 kernel is provided starting from the stable-2.13
branch of LTTng-modules. Also, tracepoint instrumentation was adapted
to follow changes to upstream kernels: the "random" tracepoint
subsystem was removed from 5.18, and this removal was backported to
stable kernels as well. Finally, a compaction subsystem instrumentation
name-spacing fix is included.
Noteworthy in the 2.13.4 release:
The same instrumentation fixes as 2.12.4 were integrated, affecting the
compaction and random subsystems. Changes to tracepoint instrumentation
were done to support the 5.18 Linux kernel, affecting the block, compaction,
sched, scsi, and kvm subsystems. The kprobes instrumentation was adapted
to use the rethooks if possible (needed for 5.18).
Now that the kvm subsystem unexports the kvm_x86_ops symbols in 5.18,
lttng-modules relies on kallsyms to use this symbol.
Finally, two changes are really more in the "bug fix" category rather than
adapting to newer kernels: the bytecode interpreter in lttng-modules left the
context fields byte order uninitialized, thus leading to bogus context field
values in the event notification capture feature. Fix this by initializing
the byte order. A hard-to-trigger race is also fixed in the event notifier
use of the ring buffer.
Changelog:
2022-06-03 (National Repeat Day) (National Repeat Day) LTTng modules 2.13.4
* Fix: event notifier: racy use of last subbuffer record
* Fix: bytecode interpreter context_get_index() leaves byte order uninitialized
* fix: 'random' tracepoints removed in stable kernels
* fix: random: remove unused tracepoints (v5.10, v5.15)
* fix: sched/tracing: Append prev_state to tp args instead (v5.18)
* fix: mm: compaction: cleanup the compaction trace events (v5.18)
* fix: scsi: core: Remove <scsi/scsi_request.h> (v5.18)
* fix: kprobes: Use rethook for kretprobe if possible (v5.18)
* fix: random: remove unused tracepoints (v5.18)
* fix: scsi: block: Remove REQ_OP_WRITE_SAME support (v5.18)
* fix: block: remove genhd.h (v5.18)
* fix: sched/tracing: Don't re-read p->state when emitting sched_switch event (v5.18)
* fix: KVM: x86: Unexport kvm_x86_ops (v5.18)
* Fix: do not warn on unknown counter ioctl
* Fix: tracepoint event: allow same provider and event name
* Fix: compaction migratepages event name
2022-06-03 (National Repeat Day) (National Repeat Day) LTTng modules 2.12.9
* fix: 'random' tracepoints removed in stable kernels
* fix: random: remove unused tracepoints (v5.10, v5.15)
* fix: random: remove unused tracepoints (v5.18)
* Document supported kernel versions for stable-2.12 branch
* Fix: include erroneously removed by backport
* Fix: tracepoint event: allow same provider and event name
* Fix: compaction migratepages event name
Project website: https://lttng.org
Documentation: https://lttng.org/docs
Download link: https://lttng.org/download
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
reply other threads:[~2022-06-03 19:30 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=846400291.20840.1654284635213.JavaMail.zimbra@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
/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).