Ryo Takakura 01b9743119 printk/panic: Allow cpu backtraces to be written into ringbuffer during panic ...

[ Upstream commit bcc954c6ca ]

commit 779dbc2e78 ("printk: Avoid non-panic CPUs writing
to ringbuffer") disabled non-panic CPUs to further write messages to
ringbuffer after panicked.

Since the commit, non-panicked CPU's are not allowed to write to
ring buffer after panicked and CPU backtrace which is triggered
after panicked to sample non-panicked CPUs' backtrace no longer
serves its function as it has nothing to print.

Fix the issue by allowing non-panicked CPUs to write into ringbuffer
while CPU backtrace is in flight.

Fixes: 779dbc2e78 ("printk: Avoid non-panic CPUs writing to ringbuffer")
Signed-off-by: Ryo Takakura <takakura@valinux.co.jp>
Reviewed-by: Petr Mladek <pmladek@suse.com>
Link: https://lore.kernel.org/r/20240812072703.339690-1-takakura@valinux.co.jp
Signed-off-by: Petr Mladek <pmladek@suse.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>

2024-08-29 17:35:53 +02:00

..

braille.c

…

braille.h

…

console_cmdline.h

Revert "printk: Save console options for add_preferred_console_match()"

2024-06-25 07:58:10 +02:00

index.c

…

internal.h

…

Makefile

Revert "printk: Save console options for add_preferred_console_match()"

2024-06-25 07:58:10 +02:00

nbcon.c

…

printk_ringbuffer.c

…

printk_ringbuffer.h

…

printk_safe.c

…

printk.c

printk/panic: Allow cpu backtraces to be written into ringbuffer during panic

2024-08-29 17:35:53 +02:00

sysctl.c

…