public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tzanussi@gmail.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] tracing/events: don't discard an event after commit
Date: Mon, 23 Mar 2009 03:33:03 -0500	[thread overview]
Message-ID: <1237797183.7527.47.camel@charm-linux> (raw)
In-Reply-To: <1237763919-21505-1-git-send-email-fweisbec@gmail.com>

Hi Frederic,

On Mon, 2009-03-23 at 00:18 +0100, Frederic Weisbecker wrote:
> Note: depends on "tracing/events: don't use wake up for events"
> 
> When we want to filter an event, the filter test is done after
> the event is commited to the ring-buffer to be discarded later if
> needed.
> 
> But a reader could be reading this event while we are trying to discard
> it. Other kind of racy events can even happen because the event is
> commited and can be read and/or consumed.
> 
> What we want is to discard the event before committing it.
> 

Thanks for fixing this - I had intend on doing this, but it completely
slipped my mind.

Thanks for all your other comments and fixes too...

Tom

> v2: add a reported-by Steven Rostedt
> 
> Reported-by: Steven Rostedt <rostedt@goodmis.org>
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> ---
>  kernel/trace/trace_events_stage_3.h |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/trace/trace_events_stage_3.h b/kernel/trace/trace_events_stage_3.h
> index 9a3bd49..9d2fa78 100644
> --- a/kernel/trace/trace_events_stage_3.h
> +++ b/kernel/trace/trace_events_stage_3.h
> @@ -222,10 +222,11 @@ static void ftrace_raw_event_##call(proto)				\
>  									\
>  	assign;								\
>  									\
> -	trace_nowake_buffer_unlock_commit(event, irq_flags, pc);	\
> -									\
>  	if (call->preds && !filter_match_preds(call, entry))		\
>  		ring_buffer_event_discard(event);			\
> +									\
> +	trace_nowake_buffer_unlock_commit(event, irq_flags, pc);	\
> +									\
>  }									\
>  									\
>  static int ftrace_raw_reg_event_##call(void)				\


      parent reply	other threads:[~2009-03-23  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-22 23:15 [PATCH] tracing/events: don't discard an event after commit Frederic Weisbecker
2009-03-22 23:18 ` [PATCH v2] " Frederic Weisbecker
2009-03-23  8:31   ` [tip:tracing/filters] " Frederic Weisbecker
2009-03-23  8:33   ` Tom Zanussi [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=1237797183.7527.47.camel@charm-linux \
    --to=tzanussi@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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