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
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [RELEASE] LTTng modules 2.8.0-rc2 (Linux kernel tracer)
Date: Tue, 26 Apr 2016 20:10:43 +0000 (UTC)	[thread overview]
Message-ID: <1570637412.70236.1461701443252.JavaMail.zimbra@efficios.com> (raw)

Hi,

This is the second release candidate of the lttng-modules 2.8 branch
of the LTTng Linux kernel tracer. As expected, it is just a bugfix release.

Let us know if you find anything, so we can sweep out any bug before
the final release!

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

Changelog:

2016-04-26 LTTng modules 2.8.0-rc2
        * Fix: writeback probe on RHEL >= 3.10.0-327.10.1
        * Fix: RHEL kernel 3.10.0-327.13.1 compat
        * Fix: ctf_user_integer should not trigger page fault
        * Fix: lib_ring_buffer_copy_from_user_inatomic error handling
        * Add comment describing ioctl number duplication
        * Fix: remove unused gfpflags.h from btrfs and compaction instrumentation
        * Fix: Remove dead code from filter interpreter
        * Fix: x86 kvm mmutrace instrumentation for kernel < 3.6
        * Fix: mm_vmscan instrumentation: remove unused gfpflags.h include
        * Fix: use of uninitialized ret value in lttng_abi_create_event
        * Fix: kmem instrumentation: remove unused gfpflags.h include
        * Fix: 4.6 kernel: use in_compat_syscall
        * Fix: use BUG_ON instead of accessing array subscript above array bounds
        * Fix: Add granularity to RHEL kernel version checks


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

                 reply	other threads:[~2016-04-26 20:10 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=1570637412.70236.1461701443252.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --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