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>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk for 5.4
Date: Mon, 16 Sep 2019 13:24:31 +0200 [thread overview]
Message-ID: <20190916112431.jsts2owcco5pg4jg@pathway.suse.cz> (raw)
Linus,
please pull the latest printk changes from
git://git.kernel.org/pub/scm/linux/kernel/git/pmladek/printk tags/printk-for-5.4
========================
- Fix off-by-one error when calculating messages that might fit
into kmsg buffer. It causes occasional omitting of the last message.
- Add missing pointer check in %pD format modifier handling.
- Some clean up.
----------------------------------------------------------------
Chuhong Yuan (1):
printk: Replace strncmp() with str_has_prefix()
James Byrne (1):
ABI: Update dev-kmsg documentation to match current kernel behaviour
Jia He (2):
vsprintf: Prevent crash when dereferencing invalid pointers for %pD
lib/test_printf: Add test of null/invalid pointer dereference for dentry
Petr Mladek (2):
lib/test_printf: Remove obvious comments from %pd and %pD tests
Merge branch 'for-5.4' into for-linus
Vincent Whitchurch (1):
printk: Do not lose last line in kmsg buffer dump
Documentation/ABI/testing/dev-kmsg | 15 +++++++--------
kernel/printk/braille.c | 15 +++++++++++----
kernel/printk/printk.c | 24 +++++++++++++++++-------
lib/test_printf.c | 5 +++++
lib/vsprintf.c | 13 ++++++++++---
5 files changed, 50 insertions(+), 22 deletions(-)
next reply other threads:[~2019-09-16 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 11:24 Petr Mladek [this message]
2019-09-21 17:10 ` [GIT PULL] printk for 5.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=20190916112431.jsts2owcco5pg4jg@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).