Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: dgoulet@efficios.com (David Goulet)
Subject: [lttng-dev] [PATCH lttng-tools] Fix: consumer data pending for empty streams
Date: Thu, 29 Aug 2013 12:54:57 -0400	[thread overview]
Message-ID: <521F7CE1.1000106@efficios.com> (raw)
In-Reply-To: <20130829024720.GA20271@Krystal>

Merged!

Mathieu Desnoyers:
> We should at least output one packet before a stream can be considered
> as readable. So far, for PID buffers, if an application exits at the
> wrong timing before a stop waiting for data pending, empty streams could
> be visible by a babeltrace executed after data pending incorrectly
> returned false.
> 
> Fix it by considering a stream for which the consumerd has written 0
> bytes to the output as having data pending.
> 
> This applies to 2.3-rc and stable-2.2.
> 
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
> ---
> diff --git a/src/common/consumer.c b/src/common/consumer.c
> index 59207da..e64e2e2 100644
> --- a/src/common/consumer.c
> +++ b/src/common/consumer.c
> @@ -498,6 +498,7 @@ struct lttng_consumer_stream *consumer_allocate_stream(uint64_t channel_key,
>  	stream->key = stream_key;
>  	stream->out_fd = -1;
>  	stream->out_fd_offset = 0;
> +	stream->output_written = 0;
>  	stream->state = state;
>  	stream->uid = uid;
>  	stream->gid = gid;
> @@ -1475,6 +1476,7 @@ ssize_t lttng_consumer_on_read_subbuffer_mmap(
>  					SYNC_FILE_RANGE_WRITE);
>  			stream->out_fd_offset += ret;
>  		}
> +		stream->output_written += ret;
>  		written += ret;
>  	}
>  	lttng_consumer_sync_trace_file(stream, orig_offset);
> @@ -1688,6 +1690,7 @@ ssize_t lttng_consumer_on_read_subbuffer_splice(
>  					SYNC_FILE_RANGE_WRITE);
>  			stream->out_fd_offset += ret_splice;
>  		}
> +		stream->output_written += ret_splice;
>  		written += ret_splice;
>  	}
>  	lttng_consumer_sync_trace_file(stream, orig_offset);
> @@ -3400,6 +3403,16 @@ int consumer_data_pending(uint64_t id)
>  		 */
>  		ret = cds_lfht_is_node_deleted(&stream->node.node);
>  		if (!ret) {
> +			/*
> +			 * An empty output file is not valid. We need at
> +			 * least one packet generated per stream, even
> +			 * if it contains no event, so it contains at
> +			 * least one packet header.
> +			 */
> +			if (stream->output_written == 0) {
> +				pthread_mutex_unlock(&stream->lock);
> +				goto data_pending;
> +			}
>  			/* Check the stream if there is data in the buffers. */
>  			ret = data_pending(stream);
>  			if (ret == 1) {
> diff --git a/src/common/consumer.h b/src/common/consumer.h
> index 2003cbe..91f6b5c 100644
> --- a/src/common/consumer.h
> +++ b/src/common/consumer.h
> @@ -221,6 +221,8 @@ struct lttng_consumer_stream {
>  	int out_fd; /* output file to write the data */
>  	/* Write position in the output file descriptor */
>  	off_t out_fd_offset;
> +	/* Amount of bytes written to the output */
> +	uint64_t output_written;
>  	enum lttng_consumer_stream_state state;
>  	int shm_fd_is_copy;
>  	int data_read;
> 



      reply	other threads:[~2013-08-29 16:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29  2:47 Mathieu Desnoyers
2013-08-29 16:54 ` David Goulet [this message]

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=521F7CE1.1000106@efficios.com \
    --to=dgoulet@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