Files
linux-bredos/include/linux
Linus Torvalds b0546776ad Merge tag 'printk-for-6.9' of git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux
Pull printk updates from Petr Mladek:
 "Improve the behavior during panic. The issues were found when testing
  the ongoing changes introducing atomic consoles and printk kthreads:

   - pr_flush() has to wait for the last reserved record instead of the
     last finalized one. Note that records are finalized in random order
     when generated by more CPUs in parallel.

   - Ignore non-finalized records during panic(). Messages printed on
     panic-CPU are always finalized. Messages printed by other CPUs
     might never be finalized when the CPUs get stopped.

   - Block new printk() calls on non-panic CPUs completely. Backtraces
     are printed before entering the panic mode. Later messages would
     just mess information printed by the panic CPU.

   - Do not take console_lock in console_flush_on_panic() at all. The
     original code did try_lock()/console_unlock(). The unlock part
     might cause a deadlock when panic() happened in a scheduler code.

   - Fix conversion of 64-bit sequence number for 32-bit atomic
     operations"

* tag 'printk-for-6.9' of git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux:
  dump_stack: Do not get cpu_sync for panic CPU
  panic: Flush kernel log buffer at the end
  printk: Avoid non-panic CPUs writing to ringbuffer
  printk: Disable passing console lock owner completely during panic()
  printk: ringbuffer: Skip non-finalized records in panic
  printk: Wait for all reserved records with pr_flush()
  printk: ringbuffer: Cleanup reader terminology
  printk: Add this_cpu_in_panic()
  printk: For @suppress_panic_printk check for other CPU in panic
  printk: ringbuffer: Clarify special lpos values
  printk: ringbuffer: Do not skip non-finalized records with prb_next_seq()
  printk: Use prb_first_seq() as base for 32bit seq macros
  printk: Adjust mapping for 32bit seq macros
  printk: nbcon: Relocate 32bit seq macros
2024-03-12 20:54:50 -07:00
..
2024-01-02 17:54:05 +01:00
2023-12-20 19:26:32 -05:00
2024-03-11 15:37:23 -07:00
2023-12-15 16:25:55 -08:00
2023-12-20 14:48:13 -08:00
2024-02-25 12:05:08 +01:00
2024-01-08 09:36:55 +09:00
2024-01-02 11:25:28 +01:00
2024-01-18 21:10:43 +01:00
2024-02-28 19:36:39 -08:00
2024-02-15 23:43:48 -05:00
2024-02-23 16:45:05 +01:00
2023-12-20 19:26:31 -05:00
2023-12-20 19:26:31 -05:00
2023-12-20 19:26:31 -05:00
2023-12-20 19:26:30 -05:00
2024-03-01 08:44:54 +00:00
2024-01-04 10:47:56 -05:00
2023-12-20 19:26:30 -05:00
2024-01-15 12:10:41 -06:00
2024-01-15 12:10:41 -06:00
2023-12-20 19:26:31 -05:00
2023-12-20 19:26:31 -05:00
2023-12-20 19:26:31 -05:00
2024-01-09 15:00:09 +01:00
2023-12-20 19:26:30 -05:00
2023-12-27 11:49:56 -05:00
2023-12-20 19:26:32 -05:00
2023-12-27 11:49:56 -05:00
2023-12-20 19:26:31 -05:00
2023-12-20 19:26:32 -05:00
2023-12-20 19:26:32 -05:00
2023-12-20 19:26:32 -05:00
2024-02-15 12:17:28 -05:00
2023-12-08 12:02:38 +01:00
2023-12-20 19:26:31 -05:00
2024-03-08 11:38:45 -08:00
2024-01-21 18:09:30 +00:00
2023-12-28 05:02:42 -08:00
2024-03-04 20:46:18 -08:00
2024-03-04 17:25:09 +01:00
2023-12-20 19:26:31 -05:00
2023-12-08 12:02:37 +01:00
2023-12-20 19:26:30 -05:00
2024-03-06 10:52:12 +01:00
2023-12-29 11:58:24 -08:00
2024-02-09 12:07:48 +00:00