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.5 - Lafontaine
Date: Mon, 3 Aug 2020 18:34:51 -0400 [thread overview]
Message-ID: <20200803223451.GA2165704@gmail.com> (raw)
Hi all,
The fifth bug-fix release of LTTng-tools 2.11 - Lafontaine has just
been released. This release addresses a number of issues listed below.
2020-08-03 lttng-tools 2.11.5 (National Watermelon Day)
* Fix: lttng: leak of userspace probe path on listing
* Fix: uprobe: missing error code on allocation failure
* Fix: sessiond: don't negate error code on list error
* Fix: send/received actual size is overwritten by 'expected' size
* Fix: partial recv lead to client disconnect
* tests: return the proper TAP exit code
* Tests: live/test_{lttng_,}kernel: use lttng_test_filter_event instead of sched_switch
* Fix: consumer: Move sanity check within `consumer_subbuffer` functions
* Cleanup: typo in DBG() statements
* Fix: relayd: send_viewer_streams sends stack data in padding
* Fix: kconsumer: missing wait for metadata thread in do_sync_metadata
* Fix: tests: interrupting get_next_notification causes test to fail
* Fix: consumer.c: wrong order of parameter in `DBG()` statement
* Fix: kernel metadata file outside of kernel/ directory
* Fix: consumer: dangling chunk on buffer allocation failure
* Fix: consumerd: uninitialized written_bytes on no-data sleep
* Build fix: consumerd misnamed label
* consumerd: on_sleep not called on stream when no data is available
* Fix: invalid discarded events on start/stop without event production
* tests: truncate metadata file for regenerate metadata test
* Fix: consumerd: user space metadata not regenerated
* Fix: tests: output_dir contains the consumerd pipe
* Fix: unix: don't PERROR on EAGAIN for non-blocking sockets
* Fix: sessiond: sessiond and agent deadlock on destroy
* Fix: incorrect specifier %lu used with size_t argument
* Fix: consumerd: live client receives incomplete metadata
* consumerd: refactor: split read_subbuf into sub-operations
* consumerd: move rotation logic to domain-agnostic read path
* sessiond: enforce mmap output type for kernel metadata channel
* consumerd: tag metadata channel as being part of a live session
* consumerd: pass channel instance to stream creation function
* consumerd: cleanup: use buffer view interface for mmap read subbuf
* consumerd: move address computation from on_read_subbuffer_mmap
* consumerd: refactor: combine duplicated check_*_functions
* kerner-ctl: add RING_RING_BUFFER_GET_NEXT_SUBBUF_METADATA_CHECK
* Add lttng_dynamic_buffer_append_view util
* Fix: lttng: Destroying session message repeated during destruction
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.5.tar.bz2
GPG signature:
https://lttng.org/files/lttng-tools/lttng-tools-2.11.5.tar.bz2.asc
reply other threads:[~2020-08-03 22:34 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=20200803223451.GA2165704@gmail.com \
--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).