x86: Stop recursive fault in print_context_stack after stack overflow
authorHugh Dickins <hughd@google.com>
Fri, 23 Mar 2012 21:02:55 +0000 (14:02 -0700)
committerIngo Molnar <mingo@kernel.org>
Sat, 24 Mar 2012 07:15:04 +0000 (08:15 +0100)
commit65c0ff4079c011232e795e62c74a0a95512b7ac3
treef578bc91f8e241c23b068bec2ecd0f58b0a322fb
parent4da7072ad6831a35a11341097ce477e18651bedd
x86: Stop recursive fault in print_context_stack after stack overflow

After printing out the first line of a stack backtrace,
print_context_stack() calls print_ftrace_graph_addr() to check
if it's making a graph of function calls, usually not the case.

But unfortunate ordering of assignments causes this to oops if
an earlier stack overflow corrupted threadinfo->task.  Reorder
to avoid that irritation.

( The fact that there was a stack overflow may often be more
  interesting than the stack that can now be shown; but
  integrating that information with this stacktrace is awkward,
  so leave it to overflow reporting. )

Signed-off-by: Hugh Dickins <hughd@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Namhyung Kim <namhyung@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Link: http://lkml.kernel.org/r/20120323225648.15DD5A033B@akpm.mtv.corp.google.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
arch/x86/kernel/dumpstack.c