Fix relayd: initialize beacon to -1ULL
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Tue, 2 Apr 2019 16:40:22 +0000 (12:40 -0400)
committerJonathan Rajotte <jonathan.rajotte-julien@efficios.com>
Wed, 10 Apr 2019 23:36:37 +0000 (19:36 -0400)
commit44a019c230262b94d8cbd2075cfbebccbe75dfc1
treef331353d3a0a073301a84aac5c7aecdce04144a9
parent6dabdfa2f97ccfd101bd119bd1ab637ddb20e22f
Fix relayd: initialize beacon to -1ULL

The relayd stream beacon_ts_end field is expected to have the value
-1ULL when unset (no beacon has been received since last index).

However, the initial state is wrong. It is left at the value 0, which
indicates that a live beacon has indeed been received (which is untrue),
which in turn causes a live beacon with ctf_stream_id of -1ULL to be
sent to babeltrace, which does not expect it, and fails.

This issue can be triggered with the following scenario:

1) create live session
2) setup UST per-uid buffers tracing
3) start tracing, without any active traced application
4) hook with babeltrace live client to view the trace
5) run a traced application

Step 5) will cause the babeltrace live client to receive a stream_id of
-1ULL, and error out.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
src/bin/lttng-relayd/stream.c
This page took 0.026248 seconds and 5 git commands to generate.