[PATCH] tracing: Remove unneeded checks from the stack tracer

From: Anton Vorontsov
Date: Wed Jul 18 2012 - 14:58:09 EST

It seems that 'ftrace_enabled' flag should not be used inside the tracer
functions. The ftrace core is using this flag for internal purposes, and
the flag wasn't meant to be used in tracers' runtime checks.

stack tracer is the only tracer that abusing the flag. So stop it from
serving as a bad example.

Also, there is a local 'stack_trace_disabled' flag in the stack tracer,
which is never updated; so it can be removed as well.

Signed-off-by: Anton Vorontsov <anton.vorontsov@xxxxxxxxxx>
kernel/trace/trace_stack.c | 4 ----
1 file changed, 4 deletions(-)

diff --git a/kernel/trace/trace_stack.c b/kernel/trace/trace_stack.c
index d4545f4..94c2c53 100644
--- a/kernel/trace/trace_stack.c
+++ b/kernel/trace/trace_stack.c
@@ -33,7 +33,6 @@ static unsigned long max_stack_size;
static arch_spinlock_t max_stack_lock =

-static int stack_trace_disabled __read_mostly;
static DEFINE_PER_CPU(int, trace_active);
static DEFINE_MUTEX(stack_sysctl_mutex);

@@ -115,9 +114,6 @@ stack_trace_call(unsigned long ip, unsigned long parent_ip)
int cpu;

- if (unlikely(!ftrace_enabled || stack_trace_disabled))
- return;

cpu = raw_smp_processor_id();

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/