From: Petr Mladek <pmladek@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Jason Wessel <jason.wessel@windriver.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
David Sterba <dsterba@suse.com>,
linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>
Subject: [PATCH v2 0/4] printk: Fixes and hardening related to KERN_CONT
Date: Wed, 9 Nov 2016 13:41:27 +0100 [thread overview]
Message-ID: <1478695291-12169-1-git-send-email-pmladek@suse.com> (raw)
The first patch fixes a messed output of continuous lines
when printing backtraces for all CPUs via NMI.
The other patches fix problems that I noticed when working
on the first patch.
I have incorporated the feedback and did much more testing.
Åll patches have changed so I did not add the taken Reviews
and Acks.
Changes against v1:
+ used const char in printk_nmi_flush_buffer()
+ print the final newline with KERN_CONT in
printk_nmi_flush_buffer()
+ used printk_skip_level() instead of the hardcoded '2'
in all patches.
+ define PRINTK_MAX_SINGLE_HEADER_LEN to avoid hardcoding
the buffer size; it simplified the code in btrfs_printk()
+ ignore KERN_CONT in __snd_printk(); the lines were hard
to read because of the added stuff like <filename:line>
for each piece.
Petr Mladek (4):
printk/NMI: Handle continuous lines and missing newline
printk/kdb: Handle more message headers
printk/btrfs: Handle more message headers
printk/sound: Handle more message headers
fs/btrfs/super.c | 26 +++++++++-------
include/linux/printk.h | 10 ++++++
kernel/debug/kdb/kdb_io.c | 2 +-
kernel/printk/nmi.c | 78 ++++++++++++++++++++++++++++++-----------------
sound/core/misc.c | 20 ++++++++----
5 files changed, 90 insertions(+), 46 deletions(-)
--
1.8.5.6
next reply other threads:[~2016-11-09 12:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 12:41 Petr Mladek [this message]
2016-11-09 12:41 ` [PATCH v2 1/4] printk/NMI: Handle continuous lines and missing newline Petr Mladek
2016-11-11 0:26 ` Sergey Senozhatsky
2016-11-11 17:28 ` Steven Rostedt
2016-11-11 18:07 ` Petr Mladek
2016-11-09 12:41 ` [PATCH v2 2/4] printk/kdb: Handle more message headers Petr Mladek
2016-11-11 17:35 ` Steven Rostedt
2016-11-11 18:13 ` Petr Mladek
2016-11-09 12:41 ` [PATCH v2 3/4] printk/btrfs: " Petr Mladek
2016-11-10 13:20 ` David Sterba
2016-11-11 17:41 ` Steven Rostedt
2016-11-11 18:16 ` Petr Mladek
2016-12-13 9:21 ` Geert Uytterhoeven
2016-12-13 13:52 ` Petr Mladek
2016-12-13 14:01 ` Geert Uytterhoeven
2016-12-13 14:26 ` David Sterba
2016-11-09 12:41 ` [PATCH v2 4/4] printk/sound: " Petr Mladek
2016-11-11 17:54 ` Steven Rostedt
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=1478695291-12169-1-git-send-email-pmladek@suse.com \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jason.wessel@windriver.com \
--cc=jbacik@fb.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®