diff options
author | Steven Rostedt <srostedt@redhat.com> | 2010-06-02 21:52:29 -0400 |
---|---|---|
committer | Steven Rostedt <rostedt@goodmis.org> | 2010-06-03 19:09:41 -0400 |
commit | d1f74e20b5b064a130cd0743a256c2d3cfe84010 (patch) | |
tree | b93ab590c24bb08f6db0dfc2a3ba60fa43af7f92 /kernel/trace/trace_functions.c | |
parent | 9dda696f0de87a2e5cfabb147e28c76b7d3c6846 (diff) | |
download | linux-d1f74e20b5b064a130cd0743a256c2d3cfe84010.tar.gz linux-d1f74e20b5b064a130cd0743a256c2d3cfe84010.tar.bz2 linux-d1f74e20b5b064a130cd0743a256c2d3cfe84010.zip |
tracing/sched: Make preempt_schedule() notrace
The function tracer code uses ftrace_preempt_disable() to disable
preemption instead of normal preempt_disable(). But there's a slight
race condition that may cause it to lose a preemption check.
This was made to keep the function tracer from recursing on itself
by disabling preemption then having the enable call the function tracer
again, causing infinite recursion.
The bug was assumed to happen if the call was just in schedule, but
this is incorrect. The bug is caused by preempt_schedule() which
is called by preempt_enable(). The calling of preempt_enable() when
NEED_RESCHED was set would call preempt_schedule() which would call
the function tracer again.
By making the preempt_schedule() and add_preempt_count() notrace
then this will prevent the inifinite recursion. This is because
the add_preempt_count() would stop the preempt_enable() in the
function tracer from calling preempt_schedule() again.
The sub_preempt_count() is also made notrace just to keep it
symmetric.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/trace_functions.c')
0 files changed, 0 insertions, 0 deletions