From: "Jérémie Galarneau" <jeremie.galarneau@efficios.com>
To: lttng-dev@lists.lttng.org
Cc: diamon-discuss@lists.linuxfoundation.org,
linux-trace-users@vger.kernel.org
Subject: [RELEASE] LTTng-tools 2.11.7 - Lafontaine
Date: Tue, 18 May 2021 19:44:17 -0400 [thread overview]
Message-ID: <YKRRUTTiUWWDfr6L@Mercury> (raw)
Hi all,
The seventh bug-fix release of LTTng-tools 2.11 - Lafontaine has just
been released. This release addresses a number of issues listed below.
2021-05-18 lttng-tools 2.11.7 (No Dirty Dishes Day)
* Fix: sessiond: leak of config_path on duplicate --config option
* Fix: relayd: live: data is missing between viewer attach and retry
* Fix: lttng-ctl: erroneous check if user is part of the tracing group
* Fix: kernel consumer: get next subbuffer EAGAIN handling
* Fix: kernel consumer: signal metadata ready condition variable
* Fix: consumerd: unbalanced subbuffer 'get' when checking operation availability
* Fix: consumerd: strlen called on uninitialized path
* Fix: tests: health thread stall: only stop consumerd when required
* Fix: tests: quote variable in case it's not set
* Fix: sessiond: session destroy hang in per-uid when context cannot be added
* Fix: lttng_destroy_session_no_wait: return 0 on success
* config: fix typo in error message
* Tests: array expressions without contant index are invalid
* Fix: validate that array expression contains constant
* Fix: test: base-path tests are not run
* Fix: filter: memory leak in filter_parser_ctx
* Fix: sessiond: fix -Wshadow error in save.c
* Fix: utils: avoid strncpy overlap in utils_partial_realpath
* Clean-up: utils: make utils_partial_realpath static
* Fix: sessiond: kernel: invalid error code check
* Fix: ust-consumer: metadata thread not woken-up after version change
* Clean-up: ust-consumer: simplify metadata cache unlock on error path
* Fix: sessiond: timer: unitiliazed sigevent fields
* Fix: sessiond: ust-registry: dereference of NULL pointer on allocation failure
* Fix: ust-consumer: metadata cache lock not taken when sampling max offset
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.11.7.tar.bz2
GPG signature:
https://lttng.org/files/lttng-tools/lttng-tools-2.11.7.tar.bz2.asc
reply other threads:[~2021-05-18 23:44 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=YKRRUTTiUWWDfr6L@Mercury \
--to=jeremie.galarneau@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).