Hugh Dickins 65c0ff4079 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>
2012-03-24 08:15:04 +01:00
..
2011-09-27 18:08:04 +02:00
2011-12-12 14:26:10 -08:00
2011-12-08 10:22:07 -08:00
2011-12-08 10:22:07 -08:00
2011-07-01 10:37:14 +02:00
2011-07-26 16:49:47 -07:00
2011-02-17 14:59:22 +01:00
2011-12-21 16:26:03 -08:00
2011-03-18 10:39:30 +01:00
2012-01-07 12:19:37 +01:00
2011-08-04 16:13:49 -07:00
2012-03-13 16:27:51 +01:00
2011-03-18 10:39:30 +01:00
2011-12-05 12:17:29 +01:00