From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] [PATCH babeltrace-1.5 0/6] Babeltrace 1.5 lttng-live with per-pid ust buffers
Date: Thu, 5 Dec 2019 01:58:03 -0500 [thread overview]
Message-ID: <20191205065809.16728-1-mathieu.desnoyers@efficios.com> (raw)
This series of fixes comes from testing babeltrace 1.5 lttng-live
under valgrind with per-pid lttng buffers. This was done in the
context of testing of the "lttng clear" feature.
Thanks,
Mathieu
Mathieu Desnoyers (6):
Fix: lttng-live: use-after-free in get_next_index()
Fix: trace-collection: trace clock use after free
Fix: lttng-live: lttng_live_open_trace_read memory leak
Fix: lib/iterator.c: unbalanced ctx put (leak)
Fix: lttng-live: ctf_live_packet_seek stream hang up handling
Fix: lttng-live format: do not error out on empty streams hang up
formats/ctf/ctf.c | 7 ++++++-
formats/lttng-live/lttng-live-comm.c | 8 ++++++--
formats/lttng-live/lttng-live-plugin.c | 1 +
lib/iterator.c | 3 +++
lib/trace-collection.c | 21 ++++++++++++++++++---
5 files changed, 34 insertions(+), 6 deletions(-)
--
2.17.1
next reply other threads:[~2019-12-05 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 6:58 Mathieu Desnoyers [this message]
2019-12-05 6:58 ` [lttng-dev] [PATCH babeltrace-1.5 1/6] Fix: lttng-live: use-after-free in get_next_index() Mathieu Desnoyers
2019-12-05 6:58 ` [lttng-dev] [PATCH babeltrace-1.5 2/6] Fix: trace-collection: trace clock use after free Mathieu Desnoyers
2019-12-05 6:58 ` [lttng-dev] [PATCH babeltrace-1.5 3/6] Fix: lttng-live: lttng_live_open_trace_read memory leak Mathieu Desnoyers
2019-12-05 6:58 ` [lttng-dev] [PATCH babeltrace-1.5 4/6] Fix: lib/iterator.c: unbalanced ctx put (leak) Mathieu Desnoyers
2019-12-05 6:58 ` [lttng-dev] [PATCH babeltrace-1.5 5/6] Fix: lttng-live: ctf_live_packet_seek stream hang up handling Mathieu Desnoyers
2019-12-05 6:58 ` [lttng-dev] [PATCH babeltrace-1.5 6/6] Fix: lttng-live format: do not error out on empty streams hang up Mathieu Desnoyers
2019-12-13 1:03 ` Jérémie Galarneau
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=20191205065809.16728-1-mathieu.desnoyers@efficios.com \
--to=mathieu.desnoyers@efficios.com \
/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