[Bug uprobes/6842] system-wide utrace syscall tracing will cause kernel panic by hackbench.
mhiramat at redhat dot com
sourceware-bugzilla@sourceware.org
Wed Aug 13 23:44:00 GMT 2008
------- Additional Comments From mhiramat at redhat dot com 2008-08-13 23:43 -------
(In reply to comment #2)
> I encountered this case even without the process("*") variant,
> and worked around it thusly in pr4225 branch:
Oh, please commit that change! :-)
> __stp_utrace_task_finder_target_death:
>
> ...
> // Call the callback
> rc = tgt->callback(tsk, 0,
> (tsk->signal == NULL) || (atomic_read(&tsk->signal->live)
> == 0),
> tgt);
> ...
By the way, I couldn't find any execution path which sets tsk->signal=NULL before
calling __stp_utrace_task_finder_target_death().(it seems released at
__exit_signal()
called from release_task()...)
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6842
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the Systemtap
mailing list