[PATCH v2 0/2] printk: CPU backtrace not printing on panic

[takakura]

From: Ryo Takakura <takakura@xxxxxxxxxxxxx>

Hi! 

This patchset fixes 2 issues on CPU backtrace during panic. The first 
issue was pointed out by John [1].

(1) The usual(non-panic context) flushing of backtraces written into 
ringbuffer does not work during panic as non-panicked CPUs can't do the 
flushing themselves.

(2) CPU backtrace triggered during panic has stopped working since the 
commit 779dbc2e78d7 ("printk: Avoid non-panic CPUs writing to ringbuffer") 
as it disabled non-panicked cpus writing into ringbuffer after panic.

Sincerely,
Ryo Takakura

---

Changes since V1:
[1] https://lore.kernel.org/all/20240729114601.176047-1-takakura@xxxxxxxxxxxxx/T/

- Thanks for the feedbacks by Petr and John.
- Fix the issue (1) seperately from original patch.
- Fix the issue (2) by allowing non-panicked CPUs to write into ringbuffer 
while CPU backtrace is triggered as suggested by Petr.

---

Ryo Takakura (2):
  Handle flushing of CPU backtraces during panic
  Allow cpu backtraces to be written into ringbuffer during panic

 include/linux/panic.h  | 1 +
 kernel/panic.c         | 9 ++++++++-
 kernel/printk/printk.c | 2 +-
 3 files changed, 10 insertions(+), 2 deletions(-)

-- 
2.34.1