Dmitry Safonov 77819daf24 kdb: don't play with console_loglevel ... Print the stack trace with KERN_EMERG - it should be always visible. Playing with console_loglevel is a bad idea as there may be more messages printed than wanted. Also the stack trace might be not printed at all if printk() was deferred and console_loglevel was raised back before the trace got flushed. Unfortunately, after rebasing on commit 2277b49258 ("kdb: Fix stack crawling on 'running' CPUs that aren't the master"), kdb_show_stack() uses now kdb_dump_stack_on_cpu(), which for now won't be converted as it uses dump_stack() instead of show_stack(). Convert for now the branch that uses show_stack() and remove console_loglevel exercise from that case. Signed-off-by: Dmitry Safonov <dima@arista.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> Acked-by: Daniel Thompson <daniel.thompson@linaro.org> Cc: Jason Wessel <jason.wessel@windriver.com> Link: http://lkml.kernel.org/r/20200418201944.482088-48-dima@arista.com Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2020-06-09 09:39:12 -07:00
..
kdb	kdb: don't play with console_loglevel	2020-06-09 09:39:12 -07:00
debug_core.c	TTY/Serial driver updates for 5.8-rc1	2020-06-07 09:52:36 -07: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