From: Petr Mladek <pmladek@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
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-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk for 5.12
Date: Mon, 22 Feb 2021 14:35:08 +0100 [thread overview]
Message-ID: <YDOy7NcXzfCJcPXw@alley> (raw)
Linus,
please pull the latest printk changes from
git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git tags/printk-for-5.12
==============================
- New "no_hash_pointers" kernel parameter causes that %p shows raw
pointer values instead of hashed ones. It is intended only for
debugging purposes. Misuse is prevented by a fat warning message
that is inspired by trace_printk().
- Prevent a possible deadlock when flushing printk_safe buffers during
panic().
- Fix performance regression caused by the lockless printk ringbuffer.
It was visible with huge log buffer and long messages.
- Documentation fix-up.
----------------------------------------------------------------
John Ogness (1):
printk: avoid prb_first_valid_seq() where possible
Lukas Bulwahn (1):
printk: rectify kernel-doc for prb_rec_init_wr()
Muchun Song (1):
printk: fix deadlock when kernel panic
Petr Mladek (2):
Merge branch 'for-5.12-no_hash_pointers' into for-linus
Merge branch 'printk-rework' into for-linus
Timur Tabi (3):
lib: use KSTM_MODULE_GLOBALS macro in kselftest drivers
kselftest: add support for skipped tests
lib/vsprintf: no_hash_pointers prints all addresses as unhashed
Documentation/admin-guide/kernel-parameters.txt | 15 +++++++++++
kernel/printk/printk.c | 28 ++++++++++++-------
kernel/printk/printk_ringbuffer.h | 2 +-
kernel/printk/printk_safe.c | 16 ++++++++---
lib/test_bitmap.c | 3 +--
lib/test_printf.c | 12 +++++++--
lib/vsprintf.c | 36 +++++++++++++++++++++++--
tools/testing/selftests/kselftest_module.h | 18 ++++++++-----
8 files changed, 103 insertions(+), 27 deletions(-)
next reply other threads:[~2021-02-22 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 13:35 Petr Mladek [this message]
2021-02-22 19:12 ` 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=YDOy7NcXzfCJcPXw@alley \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@rasmusvillemoes.dk \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--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