af2876b501
Currently, if printk lock (logbuf_lock) is held by other thread during crash, there is a chance of deadlocking the crash on next printk, and blocking a possibly desired kdump. At the start of default_machine_crash_shutdown, make printk enter NMI context, as it will use per-cpu buffers to store the message, and avoid locking logbuf_lock. Suggested-by: Michael Ellerman <mpe@ellerman.id.au> Signed-off-by: Leonardo Bras <leobras.c@gmail.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Link: https://lore.kernel.org/r/20200512214533.93878-1-leobras.c@gmail.com |
||
|---|---|---|
| .. | ||
| Makefile | ||
| core.c | ||
| core_32.c | ||
| core_64.c | ||
| crash.c | ||
| elf_64.c | ||
| file_load.c | ||
| ima.c | ||
| relocate_32.S | ||