From: "Jérémie Galarneau via lttng-dev" <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Cc: diamon-discuss <diamon-discuss@lists.linuxfoundation.org>,
linux-trace-users <linux-trace-users@vger.kernel.org>
Subject: [lttng-dev] [RELEASE] LTTng-tools 2.12.12 - (Ta) Meilleure
Date: Mon, 22 Aug 2022 16:46:26 -0400 [thread overview]
Message-ID: <YwPrIh/pVjwcqrqU@gmail.com> (raw)
Hi all,
We have just released the twelfth bug-fix release of LTTng-tools 2.12 - (Ta)
Meilleure. This release addresses a number of issues listed below.
2022-08-22 lttng-tools 2.12.12 (National Bao Day)
* Fix: waiter: futex wait: handle spurious futex wakeups
* Fix: futex wait: handle spurious futex wakeups
* Fix: utils: unhandled close return value
* Fix: agent port file is o+w when launching as root
* Fix: tests: don't assume sequential cpuids
* Fix: ust-consumerd: set `hangup_flush_done` in a locked context
* Revert "Fix: sessiond: rotation trigger leak"
* Fix: lttng-snapshot: use after free of max size argument
* Fix: lttng: snapshot: add-output: leak of max size parameter
* Tests: fix: lttng-create: leaked command parameter
* Fix: sessiond: rotation trigger leak
* Tests: fix: schedule api: leak of rotation schedule list
* Fix: lttng: enable-rotation: leak of command parameter
* Fix: lttng: track: leaked command parameter
* Fix: lttng: enable-channel: leak of popt arguments
* Tests: fix: leak of some attributes of ltt_ust_session
* Fix: liblttng-ctl: non-packed structure used for tracker serialization
* Fix: test: lttng kernel modules still loaded after running test_clock_override
As always, please report any issue you may encounter to bugs.lttng.org
or on this mailing list.
Project website: https://lttng.org
Download link:
https://lttng.org/files/lttng-tools/lttng-tools-2.12.12.tar.bz2
GPG signature:
https://lttng.org/files/lttng-tools/lttng-tools-2.12.12.tar.bz2.asc
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
reply other threads:[~2022-08-22 20:46 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=YwPrIh/pVjwcqrqU@gmail.com \
--to=lttng-dev@lists.lttng.org \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=jeremie.galarneau@efficios.com \
--cc=linux-trace-users@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).