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 7.3
Date: Wed, 19 Aug 2026 10:56:21 +0200 [thread overview]
Message-ID: <aoVvZULVPj2vH_hY@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-7.3
====================================
- Prevent a possible out-of-bound access and a use-after-free in rather
theoretical situations.
- Make no_hash_pointers take effect early.
- Some fixes and clean up of the ratelimit KUnit test.
----------------------------------------------------------------
Jia He (1):
lib/tests: test_ratelimit: fix stress test thread lifecycle and leak
John Ogness (1):
printk: Fix possible console use-after-free
Kaitao Cheng (1):
lib/vsprintf: Make no_hash_pointers take effect early
Petr Mladek (3):
printk: Handle pre-enabled consoles in the top-level register_console()
Merge branch 'for-7.3-trivial' into for-linus
Merge branch 'for-7.3-console-registration-cleanup' into for-linus
kernel/printk/printk.c | 30 +++++++++++++++++-------------
lib/tests/test_ratelimit.c | 29 +++++++++++++++++++----------
lib/vsprintf.c | 4 ++++
3 files changed, 40 insertions(+), 23 deletions(-)
next reply other threads:[~2026-08-19 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 8:56 Petr Mladek [this message]
2026-08-20 22:37 ` [GIT PULL] printk for 7.3 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=aoVvZULVPj2vH_hY@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 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.