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.18
Date: Thu, 2 Oct 2025 12:53:57 +0200	[thread overview]
Message-ID: <aN5ZxYK9vUfxXyEv@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.18

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

- Add KUnit test for the printk ring buffer.

- Fix the check of the maximal record size which is allowed to be stored
  into the printk ring buffer. It prevents corruptions of the ring buffer.

  Note that printk() is on the safe side. The messages are limited by 1kB
  buffer and are always small enough for the minimal log buffer size 4kB,
  see CONFIG_LOG_BUF_SHIFT definition.

----------------------------------------------------------------
Arnd Bergmann (1):
      printk: kunit: support offstack cpumask

John Ogness (1):
      printk: ringbuffer: Fix data block max size check

Petr Mladek (3):
      printk: ringbuffer: Explain why the KUnit test ignores failed writes
      printk: kunit: Fix __counted_by() in struct prbtest_rbdata
      Merge branch 'rework/ringbuffer-kunit-test' into for-linus

Thomas Weißschuh (1):
      printk: ringbuffer: Add KUnit test

 init/Kconfig                                 |  12 +
 kernel/printk/.kunitconfig                   |   3 +
 kernel/printk/Makefile                       |   2 +
 kernel/printk/printk_ringbuffer.c            |  48 ++--
 kernel/printk/printk_ringbuffer_kunit_test.c | 327 +++++++++++++++++++++++++++
 5 files changed, 378 insertions(+), 14 deletions(-)
 create mode 100644 kernel/printk/.kunitconfig
 create mode 100644 kernel/printk/printk_ringbuffer_kunit_test.c

             reply	other threads:[~2025-10-02 10:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 10:53 Petr Mladek [this message]
2025-10-04 19:29 ` 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=aN5ZxYK9vUfxXyEv@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®