tracing: protect reader of cmdline output
authorSteven Rostedt <srostedt@redhat.com>
Mon, 16 Mar 2009 23:20:15 +0000 (19:20 -0400)
committerSteven Rostedt <srostedt@redhat.com>
Tue, 17 Mar 2009 03:27:06 +0000 (23:27 -0400)
Impact: fix to one cause of incorrect comm outputs in trace

The spinlock only protected the creation of a comm <=> pid pair.
But it was possible that a reader could look up a pid, and get the
wrong comm because it had no locking.

This also required changing trace_find_cmdline to copy the comm cache
and not just send back a pointer to it.

Signed-off-by: Steven Rostedt <srostedt@redhat.com>

No differences found