From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] tracing: use nowakeup version of commit for function event trace tests
Date: Tue, 21 Apr 2009 00:41:30 +0200 [thread overview]
Message-ID: <20090420224129.GB5997@nowhere> (raw)
In-Reply-To: <20090420222325.267573793@goodmis.org>
On Mon, Apr 20, 2009 at 06:22:59PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt <srostedt@redhat.com>
>
> The startup tests for the event tracer also runs with the function
> tracer enabled. The "wakeup" version of the trace commit was used
> which can grab spinlocks. If a task was preempted by an NMI
> that called a function being traced, it could deadlock due to the
> function tracer trying to grab the same lock.
>
> Thanks to Frederic Weisbecker for pointing out where the bug was.
>
> Reported-by: Ingo Molnar <mingo@elte.hu>
> Reported-by: Frederic Weisbecker <fweisbec@gmail.com>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> ---
Aah, I was about to push my version, which was the same but with
a more weird changelog :-)
Frederic.
> kernel/trace/trace_events.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> index 98daf5d..672b195 100644
> --- a/kernel/trace/trace_events.c
> +++ b/kernel/trace/trace_events.c
> @@ -1164,7 +1164,7 @@ function_test_events_call(unsigned long ip, unsigned long parent_ip)
> entry->ip = ip;
> entry->parent_ip = parent_ip;
>
> - trace_current_buffer_unlock_commit(event, flags, pc);
> + trace_nowake_buffer_unlock_commit(event, flags, pc);
>
> out:
> atomic_dec(&per_cpu(test_event_disable, cpu));
> --
> 1.6.2.1
>
> --
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2009-04-20 22:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 22:22 [PATCH 0/2] [GIT PULL] tracing: various bug fixes Steven Rostedt
2009-04-20 22:22 ` [PATCH 1/2] tracing: use recursive counter over irq level Steven Rostedt
2009-04-20 22:22 ` [PATCH 2/2] tracing: use nowakeup version of commit for function event trace tests Steven Rostedt
2009-04-20 22:41 ` Frederic Weisbecker [this message]
2009-04-20 22:57 ` Steven Rostedt
2009-04-21 8:23 ` [PATCH 0/2] [GIT PULL] tracing: various bug fixes Ingo Molnar
2009-04-21 9:46 ` Ingo Molnar
2009-04-21 13:08 ` Steven Rostedt
2009-04-21 13:55 ` [PATCH][GIT PULL] ring-buffer: only warn on wrap if buffer is bigger than two pages Steven Rostedt
2009-04-21 14:35 ` Ingo Molnar
2009-04-21 14:54 ` Steven Rostedt
2009-04-21 16:22 ` Steven Rostedt
2009-04-21 14:03 ` [tip:tracing/core] " tip-bot for Steven Rostedt
2009-04-22 6:48 ` [PATCH 0/2] [GIT PULL] tracing: various bug fixes Steven Rostedt
2009-04-22 11:47 ` Frederic Weisbecker
2009-04-22 13:49 ` Steven Rostedt
2009-04-22 17:10 ` Frederic Weisbecker
2009-04-22 17:17 ` Jeremy Fitzhardinge
2009-04-22 17:22 ` Steven Rostedt
2009-04-22 21:32 ` Steven Rostedt
2009-04-23 8:28 ` Ingo Molnar
2009-04-23 3:35 ` Steven Rostedt
2009-04-23 8:20 ` Ingo Molnar
2009-04-23 13:53 ` Steven Rostedt
2009-04-23 14:39 ` Steven Rostedt
2009-04-23 15:08 ` Steven Rostedt
2009-04-23 15:11 ` Ingo Molnar
2009-04-23 16:49 ` Jeremy Fitzhardinge
2009-04-23 17:21 ` Chris Wright
2009-04-23 18:02 ` Chris Wright
2009-04-23 18:33 ` Steven Rostedt
2009-04-23 18:43 ` Chris Wright
2009-04-24 8:36 ` Ingo Molnar
2009-04-24 15:12 ` Chris Wright
2009-04-29 6:16 ` [tip:tracing/core] x86: use native register access for native tlb flushing tip-bot for Chris Wright
2009-04-23 17:52 ` [PATCH 0/2] [GIT PULL] tracing: various bug fixes Steven Rostedt
2009-04-24 8:34 ` Ingo Molnar
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=20090420224129.GB5997@nowhere \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--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