On Wed, Jul 16, 2008 at 6:13 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
quoted text
> Things get weird between lockdep and ftrace because ftrace can be called
> within lockdep internal code (via the mcount pointer) and lockdep can be
> called with ftrace (via spin_locks).
>
> Can you try this patch out and see if it fixes your problem. I only
> compiled tested it.
>
> Note: I'll be traveling for the next couple of weeks, so I will be on and
> off with email.
>
> Signed-off-by: Steven Rostedt <srostedt@redhat.com>
> ---
>  kernel/trace/trace_sched_wakeup.c |   27 ++++++++++++++++-----------
>  1 file changed, 16 insertions(+), 11 deletions(-)

Works for me! :-)

There's no warning during self-tests. But then again, I didn't try
tracing anything else either.


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
unsubscribe notice
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/