From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: ltt-dev@lists.casi.polymtl.ca
Cc: linux-kernel@vger.kernel.org
Subject: [RELEASE] LTTng 0.205, 0.206, ltt-control 0.82 for Linux 2.6.33.2
Date: Fri, 2 Apr 2010 20:44:57 -0400 [thread overview]
Message-ID: <20100403004457.GA5992@Krystal> (raw)
Hi,
Here come the latest LTTng versions, bringing mostly bugfixes:
- LTTng 0.205 fixes a kref race in channel teardown vs lttd file open.
- LTTng 0.206 marks Immediate Values as BROKEN for PowerPC. Will be replaced by
asm goto from mainline eventually anyway, so don't bother looking for the
cause of the bug.
- ltt-control 0.82 ensures lttctl waits for lttd to complete when called at
trace destruction in overwrite mode. Failure to do so can result in unread
channels in flight recorder mode.
Thanks,
Mathieu
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next reply other threads:[~2010-04-03 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 0:44 Mathieu Desnoyers [this message]
2010-04-03 0:58 ` [ltt-dev] [RELEASE] LTTng 0.205, 0.206, ltt-control 0.82 for Linux 2.6.33.2 Mathieu Desnoyers
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=20100403004457.GA5992@Krystal \
--to=mathieu.desnoyers@efficios.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
/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