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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 12 Feb 2019 18:47:19 +0000 (19:47 +0100)
commit3818c29a65d6af5d53a977a4078d8cc94eb553e8
tree6473938e7b80fffad24d9b7fb63a7f884428407a
parent6a7c0215d28c6ec1482d3aa5bf28d88c2070f426
kdb: Don't back trace on a cpu that didn't round up

[ Upstream commit 162bc7f5afd75b72acbe3c5f3488ef7e64a3fe36 ]

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>
Signed-off-by: Sasha Levin <sashal@kernel.org>
kernel/debug/debug_core.c
kernel/debug/kdb/kdb_bt.c
kernel/debug/kdb/kdb_debugger.c