Re: [PATCH 0/4] [GIT PULL] tracing: recursion and compile fixes
From: Steven Rostedt
Date: Mon Apr 20 2009 - 15:53:25 EST
On Mon, 20 Apr 2009, Frederic Weisbecker wrote:
> On Mon, Apr 20, 2009 at 09:28:03PM +0200, Ingo Molnar wrote:
> > [ 16.176013] Call Trace:
> > [ 16.176013] [<80944340>] ? printk+0x15/0x1d
> > [ 16.176013] [<803a410a>] _raw_spin_lock+0x19a/0x1b0
> > [ 16.176013] [<80947bb7>] _spin_lock_irqsave+0x57/0x70
> > [ 16.176013] [<8012b2ca>] __wake_up+0x1a/0x50
> > [ 16.176013] [<8019392f>] trace_wake_up+0x2f/0x40
>
>
> The function tracer, used in the selftest, uses trace_current_buffer_unlock_commit
> which in turn calls trace_wake_up.
>
> The function tracer shouldn't call trace_wake_up() (might hold
> the rq lock already).
Ug, I meant to update that :-p
>
> I'm preparing a fix.
>
Thanks,
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/