All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: John Ogness <john.ogness@linutronix.de>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Peter Zijlstra <peterz@infradead.org>,
	Petr Mladek <pmladek@suse.com>,
	printk@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Few printk fixups for 7.4
Date: Fri, 6 Nov 2026 11:48:16 +0100	[thread overview]
Message-ID: <au2wcOTpkirvACU6@pathway.suse.cz> (raw)

Hi Linus,

please pull few printk fixups from

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

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

- Prevent possible use-after-free when printk kthreads could not be created

- Fix computation of the free space when allocating a bigger ring buffer

- Add info about the new printk mailing list for printk-related subsystems

----------------------------------------------------------------
John Ogness (1):
      printk: Avoid multiple unregistration in unregister_console_locked()

Petr Mladek (1):
      MAINTAINERS: Add new "printk" mailing list for PRINTK, PRINTK INDEXING, and VSPRINTF

Wang Wensheng (1):
      printk_ringbuffer: Fix space_used() when blk_lpos->next overflows

 MAINTAINERS                       |  3 +++
 kernel/printk/printk.c            | 34 ++++++++++++++++++++++++++++++----
 kernel/printk/printk_ringbuffer.c |  8 +++-----
 3 files changed, 36 insertions(+), 9 deletions(-)

             reply	other threads:[~2026-11-06 10:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 10:48 Petr Mladek [this message]
2026-11-06 21:47 ` [GIT PULL] Few printk fixups for 7.4 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=au2wcOTpkirvACU6@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=printk@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.