No description
Find a file
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
arch x86/amd_gart: print stacktrace for a leak with KERN_ERR 2020-06-09 09:39:12 -07:00
block
certs
crypto
Documentation remoteproc updates for v5.8 2020-06-08 13:01:08 -07:00
drivers power: use show_stack_loglvl() 2020-06-09 09:39:12 -07:00
fs The highlights are: 2020-06-08 12:49:18 -07:00
include sysrq: use show_stack_loglvl() 2020-06-09 09:39:12 -07:00
init
ipc
kernel kdb: don't play with console_loglevel 2020-06-09 09:39:12 -07:00
lib
LICENSES
mm
net The highlights are: 2020-06-08 12:49:18 -07:00
samples
scripts
security
sound
tools kallsyms/printk: add loglvl to print_ip_sym() 2020-06-09 09:39:10 -07:00
usr
virt
.clang-format
.cocciconfig
.get_maintainer.ignore
.gitattributes
.gitignore
.mailmap
COPYING
CREDITS
Kbuild
Kconfig
MAINTAINERS remoteproc updates for v5.8 2020-06-08 13:01:08 -07:00
Makefile
README

Linux kernel
============

There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.

In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``.  The formatted documentation can also be read online at:

    https://www.kernel.org/doc/html/latest/

There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.

Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.