https://bugs.lttng.org/https://bugs.lttng.org/themes/lttng/favicon/a.ico?14249722912015-09-29T18:55:35ZLTTng bugs repositoryLTTng-tools - Bug #942: Listing a session's kernel events after enabling a syscall does not produce the same output before/after tracing is started.https://bugs.lttng.org/issues/942?journal_id=27712015-09-29T18:55:35ZJérémie Galarneaujeremie.galarneau@efficios.com
<ul></ul><pre>
$ uname -a
Linux XThink 4.1.6-1-ARCH #1 SMP PREEMPT Mon Aug 17 08:52:28 CEST 2015 x86_64 GNU/Linux
lttng-modules master @ 0112cb7
</pre> LTTng-tools - Bug #942: Listing a session's kernel events after enabling a syscall does not produce the same output before/after tracing is started.https://bugs.lttng.org/issues/942?journal_id=28602016-03-08T16:03:38ZMathieu Desnoyersmathieu.desnoyers@efficios.com
<ul><li><strong>Project</strong> changed from <i>LTTng-modules</i> to <i>LTTng-tools</i></li><li><strong>Target version</strong> set to <i>2.7</i></li></ul><p>This appears to be an issue in the LTTng Tools command line interface (list.c).</p> LTTng-tools - Bug #942: Listing a session's kernel events after enabling a syscall does not produce the same output before/after tracing is started.https://bugs.lttng.org/issues/942?journal_id=29382016-05-05T02:58:36ZJérémie Galarneaujeremie.galarneau@efficios.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>Mathieu Desnoyers</i></li></ul><p>Appears to be fixed in master, but it is not clear when the fix was introduced.</p>
<p>I seem to remember that lttng-modules was listing tracepoints rather than enablers. Mathieu, does it ring a bell?<br />(assigning to get feedback)</p> LTTng-tools - Bug #942: Listing a session's kernel events after enabling a syscall does not produce the same output before/after tracing is started.https://bugs.lttng.org/issues/942?journal_id=29792016-05-10T19:12:52ZMathieu Desnoyersmathieu.desnoyers@efficios.com
<ul></ul><p>I don't think it was caused by lttng-modules. I would think the following tools commits are responsible for fixing this (they appear in stable-2.7 too):</p>
<pre>
commit 9897fbc95aea23f996b7543d86363a3dd72a0c53
Author: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Date: Tue Mar 8 12:08:12 2016 -0500
Fix: Only save kernel enablers in session configuration
The session configuration serialization currently saves the
kernel enablers along with all enabled syscalls. In the case
where a syscall would be enabled with a given filter, this would
result in two events being enabled:
1) the syscall with its filter expression (the enabler)
2) the syscall on its own (an enabled syscall)
The observable effect of this is that the syscall ends up being
traced regardless of the filter's evaluation.
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
commit db906c125f293467e08c043f27d2797fb748b23e
Author: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Date: Tue Mar 8 12:06:14 2016 -0500
Fix: Only list kernel enablers when listing events
lttng list would list kernel enablers and individual enabled
syscalls which would result in a confusing output.
For instance, enabling the "open" syscall with a filter would
result in a list output displaying both the enabler,
the syscall's name + its filter, and the syscall on its own,
without any mention of an enabled filter.
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
commit da60cf073ac81b8f903af876c31bd0a94c053c4b
Author: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Date: Tue Mar 8 11:11:33 2016 -0500
Fix: syscalls hash table leaks when listing kernel events
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
</pre> LTTng-tools - Bug #942: Listing a session's kernel events after enabling a syscall does not produce the same output before/after tracing is started.https://bugs.lttng.org/issues/942?journal_id=29852016-05-11T19:56:05ZMathieu Desnoyersmathieu.desnoyers@efficios.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul>