kdb: Don't back trace on a cpu that didn't round up
authorDouglas Anderson <dianders@chromium.org>
Wed, 5 Dec 2018 03:38:28 +0000 (19:38 -0800)
committerDaniel Thompson <daniel.thompson@linaro.org>
Sun, 30 Dec 2018 08:31:23 +0000 (08:31 +0000)
commit162bc7f5afd75b72acbe3c5f3488ef7e64a3fe36
tree28a6c66c667177ad20271d85d332f0e3831b955f
parent87b095928584da7d5cb3149016f00b0b139c2292
kdb: Don't back trace on a cpu that didn't round up

If you have a CPU that fails to round up and then run 'btc' you'll end
up crashing in kdb becaue we dereferenced NULL.  Let's add a check.
It's wise to also set the task to NULL when leaving the debugger so
that if we fail to round up on a later entry into the debugger we
won't backtrace a stale task.

Signed-off-by: Douglas Anderson <dianders@chromium.org>
Acked-by: Daniel Thompson <daniel.thompson@linaro.org>
Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
kernel/debug/debug_core.c
kernel/debug/kdb/kdb_bt.c
kernel/debug/kdb/kdb_debugger.c