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>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>, Jan Kara <jack@suse.cz>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk for 5.20
Date: Mon, 1 Aug 2022 17:07:56 +0200 [thread overview]
Message-ID: <YufsTLpighCI7qSf@alley> (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-5.20
=====================================
- Completely disable printing on consoles with CONFIG_RT. They break
RT guarantees. They are too slow to be called with raw spinlocks.
They can't be called with normal spinlocks in an atomic context because
RT spinlocks might sleep. It is going to get fixed by the kthreads and
atomic consoles. In the meantime, the debugging of CONFIG_RT kernel
will be possible only by the user space kernel log readers.
- Allow to read kernel log in gdb even on 32 bits systems.
- More granular check of the buffer usage in printf selftest.
- Clang warning fix.
----------------------------------------------------------------
Antonio Borneo (1):
scripts/gdb: fix 'lx-dmesg' on 32 bits arch
Justin Stitt (1):
lib/test_printf.c: fix clang -Wformat warnings
Petr Mladek (2):
Merge branch 'for-5.20' into for-linus
Merge branch 'rework/kthreads' into for-linus
Rasmus Villemoes (1):
lib/test_printf.c: split write-beyond-buffer check in two
Sebastian Andrzej Siewior (1):
printk: Skip console drivers on PREEMPT_RT.
kernel/printk/printk.c | 10 ++++++++++
lib/test_printf.c | 21 +++++++++++++++++----
scripts/gdb/linux/dmesg.py | 9 +++------
scripts/gdb/linux/utils.py | 14 ++++++++++++--
4 files changed, 42 insertions(+), 12 deletions(-)
next reply other threads:[~2022-08-01 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 15:07 Petr Mladek [this message]
2022-08-01 15:45 ` [GIT PULL] printk for 5.20 David Laight
2022-08-02 7:37 ` Petr Mladek
2022-08-03 3:19 ` Linus Torvalds
2022-08-03 14:35 ` Sebastian Andrzej Siewior
2022-08-03 14:46 ` David Laight
2022-08-03 15:43 ` Petr Mladek
2022-08-03 16:06 ` Steven Rostedt
2022-08-03 16:08 ` Linus Torvalds
2022-08-03 16:34 ` Sebastian Andrzej Siewior
2022-08-03 17:08 ` Ingo Molnar
2022-08-09 1:18 ` Thomas Gleixner
2022-08-11 13:38 ` Daniel Vetter
2022-08-11 13:38 ` Daniel Vetter
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=YufsTLpighCI7qSf@alley \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=jack@suse.cz \
--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=tglx@linutronix.de \
--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.