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>,
	Petr Mladek <pmladek@suse.com>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk for 6.14
Date: Mon, 20 Jan 2025 14:22:26 +0100	[thread overview]
Message-ID: <Z45OEv0jeo0BkfsT@pathway.suse.cz> (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.14

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

- Prevent possible deadlocks, caused by the lock serializing per-CPU
  backtraces, by entering the deferred printk context.

- Enforce the right casting in LOG_BUF_LEN_MAX definition.

----------------------------------------------------------------
John Ogness (2):
      printk: Remove redundant deferred check in vprintk()
      printk: Defer legacy printing when holding printk_cpu_sync

Kuan-Wei Chiu (1):
      printk: Fix signed integer overflow when defining LOG_BUF_LEN_MAX

Petr Mladek (1):
      Merge branch 'for-6.14-cpu_sync-fixup' into for-linus

 kernel/printk/internal.h    |  6 ++++++
 kernel/printk/printk.c      |  7 ++++++-
 kernel/printk/printk_safe.c | 16 ++++++----------
 3 files changed, 18 insertions(+), 11 deletions(-)

             reply	other threads:[~2025-01-20 13:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20 13:22 Petr Mladek [this message]
2025-01-21 23:04 ` 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=Z45OEv0jeo0BkfsT@pathway.suse.cz \
    --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®