summaryrefslogtreecommitdiffstats
path: root/mm/util.c
diff options
context:
space:
mode:
authorDmitry Safonov <dima@arista.com>2020-06-08 21:30:07 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2020-06-09 09:39:10 -0700
commit5489ab50c22771ddcad014968141b0d104d650a3 (patch)
treeda45382c2f04f70bf5f8abecb8132baf70f38874 /mm/util.c
parent8ca4d19932a5649930db29202b285d8e4e96a98a (diff)
downloadlinux-stable-5489ab50c22771ddcad014968141b0d104d650a3.tar.gz
linux-stable-5489ab50c22771ddcad014968141b0d104d650a3.tar.bz2
linux-stable-5489ab50c22771ddcad014968141b0d104d650a3.zip
arm/asm: add loglvl to c_backtrace()
Currently, the log-level of show_stack() depends on a platform realization. It creates situations where the headers are printed with lower log level or higher than the stacktrace (depending on a platform or user). Furthermore, it forces the logic decision from user to an architecture side. In result, some users as sysrq/kdb/etc are doing tricks with temporary rising console_loglevel while printing their messages. And in result it not only may print unwanted messages from other CPUs, but also omit printing at all in the unlucky case where the printk() was deferred. Introducing log-level parameter and KERN_UNSUPPRESSED [1] seems an easier approach than introducing more printk buffers. Also, it will consolidate printings with headers. Add log level argument to c_backtrace() as a preparation for introducing show_stack_loglvl(). [1]: https://lore.kernel.org/lkml/20190528002412.1625-1-dima@arista.com/T/#u Signed-off-by: Dmitry Safonov <dima@arista.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Cc: Russell King <linux@armlinux.org.uk> Cc: Will Deacon <will@kernel.org> Link: http://lkml.kernel.org/r/20200418201944.482088-5-dima@arista.com Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/util.c')
0 files changed, 0 insertions, 0 deletions