The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Ogness <john.ogness@linutronix.de>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>, Jan Kara <jack@suse.cz>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk for 6.9
Date: Tue, 12 Mar 2024 15:54:57 +0100	[thread overview]
Message-ID: <ZfBswbsqObB4H73_@alley> (raw)

Hi Linus,

please pull the latest printk changes from

  git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git tags/printk-for-6.9

========================================

Printk changes for 6.9 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.

----------------------------------------------------------------
John Ogness (12):
      printk: nbcon: Relocate 32bit seq macros
      printk: Use prb_first_seq() as base for 32bit seq macros
      printk: ringbuffer: Do not skip non-finalized records with prb_next_seq()
      printk: ringbuffer: Clarify special lpos values
      printk: For @suppress_panic_printk check for other CPU in panic
      printk: Add this_cpu_in_panic()
      printk: ringbuffer: Cleanup reader terminology
      printk: Wait for all reserved records with pr_flush()
      printk: ringbuffer: Skip non-finalized records in panic
      printk: Avoid non-panic CPUs writing to ringbuffer
      panic: Flush kernel log buffer at the end
      dump_stack: Do not get cpu_sync for panic CPU

Petr Mladek (1):
      printk: Disable passing console lock owner completely during panic()

Sebastian Andrzej Siewior (1):
      printk: Adjust mapping for 32bit seq macros

 include/linux/printk.h            |   2 +
 kernel/panic.c                    |   8 +
 kernel/printk/nbcon.c             |  41 +----
 kernel/printk/printk.c            | 101 +++++++-----
 kernel/printk/printk_ringbuffer.c | 337 ++++++++++++++++++++++++++++++++------
 kernel/printk/printk_ringbuffer.h |  54 +++++-
 lib/dump_stack.c                  |  16 +-
 7 files changed, 420 insertions(+), 139 deletions(-)

             reply	other threads:[~2024-03-12 14:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 14:54 Petr Mladek [this message]
2024-03-13  4:12 ` [GIT PULL] printk for 6.9 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZfBswbsqObB4H73_@alley \
    --to=pmladek@suse.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bigeasy@linutronix.de \
    --cc=jack@suse.cz \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox