archive mirror
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <>
Subject: [RELEASE] LTTng-modules 2.13.2 (Linux kernel tracer)
Date: Mon, 7 Mar 2022 16:17:55 -0500 (EST)	[thread overview]
Message-ID: <> (raw)


The 2.13.2 release of the LTTng kernel tracer includes a fix for the
syscall tracing feature. A bug crept into 2.13.0 which caused the
system call input arguments to be recorded on return from system call
rather than the output arguments. This fix was in the master branch of
lttng-modules, but was not cherry-picked into the 2.13 stable branch.

This missing backport went unnoticed through our CI integration       
because the relevant kernel tracer tests were not part of lttng-tools 
default test suite: "make check". This is now fixed in the lttng-tools

This release also contains commits needed to trace the 5.17 kernels
(currently at v5.17-rc7).

Users of lttng-modules 2.13.0 and 2.13.1 should upgrade to 2.13.2
if they want to gather useful output arguments on return from system
call into their trace, rather than an extra copy of the system call
input arguments.




2022-03-07 (National Cereal Day) LTTng modules 2.13.2
        * Fix: incorrect in/out direction for syscall exit
        * fix: net: socket: rename SKB_DROP_REASON_SOCKET_FILTER (v5.17)
        * fix: net: skb: introduce kfree_skb_reason() (v5.17)
        * fix: random: rather than entropy_store abstraction, use global (v5.17)
        * fix: btrfs: pass fs_info to trace_btrfs_transaction_commit (v5.17)
        * fix: mm: compaction: fix the migration stats in trace_mm_compaction_migratepages() (v5.17)
        * fix: block: remove the ->rq_disk field in struct request (v5.17)
        * fix: block: remove GENHD_FL_SUPPRESS_PARTITION_INFO (v5.17)
        * Copyright ownership transfer

Project website:
Download link:

Mathieu Desnoyers
EfficiOS Inc.

                 reply	other threads:[~2022-03-07 21:26 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).