Douglas Anderson 9441d5f6b7 kdb: Gid rid of implicit setting of the current task / regs ... Some (but not all?) of the kdb backtrace paths would cause the kdb_current_task and kdb_current_regs to remain changed. As discussed in a review of a previous patch [1], this doesn't seem intuitive, so let's fix that. ...but, it turns out that there's actually no longer any reason to set the current task / current regs while backtracing anymore anyway. As of commit 2277b49258 ("kdb: Fix stack crawling on 'running' CPUs that aren't the master") if we're backtracing on a task running on a CPU we ask that CPU to do the backtrace itself. Linux can do that without anything fancy. If we're doing backtrace on a sleeping task we can also do that fine without updating globals. So this patch mostly just turns into deleting a bunch of code. [1] https://lore.kernel.org/r/20191010150735.dhrj3pbjgmjrdpwr@holly.lan Signed-off-by: Douglas Anderson <dianders@chromium.org> Link: https://lore.kernel.org/r/20191109111624.4.Ibc3d982bbeb9e46872d43973ba808cd4c79537c7@changeid Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>		2020-01-31 17:34:00 +00:00
..
kdb	kdb: Gid rid of implicit setting of the current task / regs	2020-01-31 17:34:00 +00:00
debug_core.c	kdb: Avoid array subscript warnings on non-SMP builds	2019-10-24 15:34:58 +01:00
debug_core.h	kdb: Fix stack crawling on 'running' CPUs that aren't the master	2019-10-10 16:28:48 +01:00
gdbstub.c	gdbstub: Replace strcpy() by strscpy()	2019-05-02 13:40:27 +01:00
Makefile	treewide: Add SPDX license identifier - Makefile/Kconfig	2019-05-21 10:50:46 +02:00