softlockup: serialized softlockup's log
authorLi Zhe <lizhe.67@bytedance.com>
Thu, 23 Nov 2023 08:40:22 +0000 (16:40 +0800)
committerAndrew Morton <akpm@linux-foundation.org>
Mon, 11 Dec 2023 01:21:44 +0000 (17:21 -0800)
commit9d02330abd3ecdacc43fc6b16a5668e7e94b7562
tree019f798651b2d5a714eacf0b0fa3c290324b389f
parentb3ba234171cd0d58df0a13c262210ff8b5fd2830
softlockup: serialized softlockup's log

If multiple CPUs trigger softlockup at the same time with
'softlockup_all_cpu_backtrace=0', the softlockup's logs will appear
staggeredly in dmesg, which will affect the viewing of the logs for
developer.  Since the code path for outputting softlockup logs is not a
kernel hotspot and the performance requirements for the code are not
strict, locks are used to serialize the softlockup log output to improve
the readability of the logs.

Link: https://lkml.kernel.org/r/20231123084022.10302-1-lizhe.67@bytedance.com
Signed-off-by: Li Zhe <lizhe.67@bytedance.com>
Reviewed-by: Petr Mladek <pmladek@suse.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Cc: Lecopzer Chen <lecopzer.chen@mediatek.com>
Cc: Pingfan Liu <kernelfans@gmail.com>
Cc: Zefan Li <lizefan.x@bytedance.com>
Cc: John Ogness <john.ogness@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
kernel/watchdog.c