public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev@lists.lttng.org,
	diamon-discuss@lists.linuxfoundation.org,
	linux-trace-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RELEASE] LTTng-modules 2.13.15 (Linux kernel tracer)
Date: Sat, 28 Sep 2024 10:59:17 -0400	[thread overview]
Message-ID: <e367cf33-e113-4fb8-9f48-94bb7a531604@efficios.com> (raw)

Hi,

This is a stable release announcement for the LTTng kernel tracer,
an out-of-tree kernel tracer for the Linux kernel.

The LTTng project provides low-overhead, correlated userspace and
kernel tracing on Linux. Its use of the Common Trace Format and a
flexible control interface allows it to fulfill various workloads.

* New in this release: Introduce support for Linux v6.11.

Detailed change log:

2024-09-28 (Ask a Stupid Question Day) LTTng modules 2.13.15
         * Fix: scsi: sd: Atomic write support added in 6.11-rc1
         * Fix: block_start removed from btrfs_get_extent in 6.11-rc1
         * Fix: block_len removed frmo btrfs_get_extent in 6.11-rc1
         * Fix: orig_start removed from btrfs_get_extent in 6.11-rc1
         * Fix: ext4_da_reserve_space changed in 6.11-rc1
         * Fix: kfree_skb changed in 6.11-rc1
         * Fix: event notifier: set eval_capture to false for kprobe and uprobe

Project website: https://lttng.org
Documentation: https://lttng.org/docs
Download link: https://lttng.org/download

-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com

                 reply	other threads:[~2024-09-28 15: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=e367cf33-e113-4fb8-9f48-94bb7a531604@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-users@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