x86: Fix dumpstack_64 to keep state of "used" variable in loop
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>
Wed, 2 Apr 2014 17:26:40 +0000 (13:26 -0400)
committerLinus Torvalds <torvalds@linux-foundation.org>
Wed, 2 Apr 2014 18:46:50 +0000 (11:46 -0700)
commit1aabc5990d205cdb0789a1c26143c53601e9bb07
tree01e0db2ac388f630d964b2b33365af9d77307fb5
parentb33ce442993865180292df2a314ee5251ba38b50
x86: Fix dumpstack_64 to keep state of "used" variable in loop

Commit 2223f6f6eeaa "x86: Clean up dumpstack_64.c code" moved the used
variable to a local within the loop, but the in_exception_stack()
depended on being non-volatile with the ability to change it.

By always re-initializing the "used" variable to zero, it would cause
the in_exception_stack() to return the same thing each time, and
cause the dump_stack loop to go into an infinite loop.

Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
arch/x86/kernel/dumpstack_64.c