From: Russell King <rmk@dyn-67.arm.linux.org.uk>
Date: Thu, 5 Jul 2007 18:59:51 +0000 (+0100)
Subject: [ARM] always allow dump_stack() to produce a backtrace
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=082f47a79bfc8a526b9a3e14a0ae9504fc09cc12;p=GitHub%2Fmt8127%2Fandroid_kernel_alcatel_ttab.git

[ARM] always allow dump_stack() to produce a backtrace

Don't make this dependent on CONFIG_DEBUG_KERNEL - if we hit a WARN_ON
we need the stack trace to work out how we got to that point.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
---

diff --git a/arch/arm/kernel/traps.c b/arch/arm/kernel/traps.c
index 1b68d365d0e1..237f4999b9a1 100644
--- a/arch/arm/kernel/traps.c
+++ b/arch/arm/kernel/traps.c
@@ -181,9 +181,7 @@ static void dump_backtrace(struct pt_regs *regs, struct task_struct *tsk)
 
 void dump_stack(void)
 {
-#ifdef CONFIG_DEBUG_ERRORS
 	__backtrace();
-#endif
 }
 
 EXPORT_SYMBOL(dump_stack);