Re: [PATCH] tracing: kill wrong message when cat tracing/trace

[Steven Rostedt]

On Mon, 2010-04-05 at 17:11 +0800, Lai Jiangshan wrote:
> Because of a local variable is not initialized, I got these
> when I did 'cat tracing/trace'. (not trace_pipe):
> 
> CPU:0 [LOST 18446744071579453134 EVENTS]
>               ps-3099  [000]   560.770221: lock_acquire: ffff880030865010 &(&dentry->d_lock)->rlock
> CPU:0 [LOST 18446744071579453134 EVENTS]
>               ps-3099  [000]   560.770221: lock_release: ffff880030865010 &(&dentry->d_lock)->rlock
> CPU:0 [LOST 18446612133255294080 EVENTS]
>               ps-3099  [000]   560.770221: lock_acquire: ffff880030865010 &(&dentry->d_lock)->rlock
> CPU:0 [LOST 18446744071579453134 EVENTS]
>               ps-3099  [000]   560.770222: lock_release: ffff880030865010 &(&dentry->d_lock)->rlock
> CPU:0 [LOST 18446744071579453134 EVENTS]
>               ps-3099  [000]   560.770222: lock_release: ffffffff816cfb98 dcache_lock
> 
> See peek_next_entry(), it does not set *lost_events when we 'cat tracing/trace'
> 
> Signed-off-by: Lai Jiangshan <laijs@xxxxxxxxxxxxxx>

Applied, Thanks Lai!

-- 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/