iv/linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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>
This commit is contained in:
Russell King 2007-07-05 19:59:51 +01:00 committed by Russell King
parent 7b9c7b4d07
commit 082f47a79b
1 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
arch/arm/kernel/traps.c
View File

@ -181,9 +181,7 @@ static void dump_backtrace(struct pt_regs *regs, struct task_struct *tsk)
void dump_stack(void) void dump_stack(void)
{ {
#ifdef CONFIG_DEBUG_ERRORS
__backtrace(); __backtrace();
#endif
} }
EXPORT_SYMBOL(dump_stack); EXPORT_SYMBOL(dump_stack);