mirror of https://lore.kernel.org/lkml/
 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>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk for 5.18
Date: Mon, 21 Mar 2022 15:28:26 +0100	[thread overview]
Message-ID: <YjiLijmVZGox94IH@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-5.18

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

- Make %pK behave the same as %p for kptr_restrict == 0 also
  with no_hash_pointers parameter.

- Ignore the default console in the device tree also when console=null
  or console="" is used on the command line.

- Document console=null and console="" behavior.

- Prevent a deadlock and a livelock caused by console_lock in panic().

- Make console_lock available for panicking CPU.

- Fast query for the next to-be-used sequence number.

- Use the expected return values in printk.devkmsg __setup handler.

- Use the correct atomic operations in wake_up_klogd() irq_work handler.

- Avoid possible unaligned access when handling %4cc printing format.

----------------------------------------------------------------
Andre Kalb (1):
      printk: Set console_set_on_cmdline=1 when __add_preferred_console() is called with user_specified == true

Andy Shevchenko (2):
      vsprintf: Fix potential unaligned access
      vsprintf: Move space out of string literals in fourcc_string()

Christophe Leroy (1):
      vsprintf: Fix %pK with kptr_restrict == 0

Jiapeng Chong (1):
      printk: make suppress_panic_printk static

John Ogness (1):
      printk: use atomic updates for klogd work

Petr Mladek (4):
      printk: ringbuffer: Improve prb_next_seq() performance
      Merge branch 'for-5.18-vsprintf-fourcc-fixup' into for-linus
      Merge branch 'for-5.18-panic-deadlocks' into for-linus
      Merge branch 'rework/fast-next-seq' into for-linus

Randy Dunlap (2):
      Docs: printk: add 'console=null|""' to admin/kernel-parameters
      printk: fix return value of printk.devkmsg __setup handler

Stephen Brennan (4):
      printk: Add panic_in_progress helper
      printk: disable optimistic spin during panic
      printk: Avoid livelock with heavy printk during panic
      printk: Drop console_sem during panic

 Documentation/admin-guide/kernel-parameters.txt |  9 ++-
 kernel/printk/printk.c                          | 85 ++++++++++++++++++++++---
 kernel/printk/printk_ringbuffer.c               | 52 +++++++++++++--
 kernel/printk/printk_ringbuffer.h               |  2 +
 lib/vsprintf.c                                  | 49 ++++++++------
 5 files changed, 161 insertions(+), 36 deletions(-)

             reply	other threads:[~2022-03-21 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 14:28 Petr Mladek [this message]
2022-03-23 19:26 ` 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=YjiLijmVZGox94IH@alley \
    --to=pmladek@suse.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --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=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

all inboxes | Powered by JetHome®