public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] printk for 4.11
Date: Wed, 22 Feb 2017 12:47:06 +0100	[thread overview]
Message-ID: <20170222114705.GA30336@linux.suse> (raw)

Linus,

please pull from

  git://git.kernel.org/pub/scm/linux/kernel/git/pmladek/printk.git for-linus

to receive printk queue for 4.11 merge window:

==========

- Add Petr Mladek, Sergey Senozhatsky as printk maintainers,
  and Steven Rostedt as the printk reviewer. This idea came up
  after the discussion about printk issues at Kernel Summit.
  It was formulated and discussed at lkml[1].


- Extend a lock-less NMI per-cpu buffers idea to handle recursive
  printk() calls by Sergey Senozhatsky[2]. It is the first step
  in sanitizing printk as discussed at Kernel Summit.

  The change allows to see messages that would normally get ignored
  or would cause a deadlock.

  Also it allows to enable lockdep in printk(). This already paid
  off. The testing in linux-next helped to discover two old
  problems that were hidden before[3][4].


- Remove unused parameter by Sergey Senozhatsky. Clean up
  after a past change.


[1] http://lkml.kernel.org/r/1481798878-31898-1-git-send-email-pmladek@suse.com
[2] http://lkml.kernel.org/r/20161227141611.940-1-sergey.senozhatsky@gmail.com
[3] http://lkml.kernel.org/r/20170215044332.30449-1-sergey.senozhatsky@gmail.com
[4] http://lkml.kernel.org/r/20170217015932.11898-1-sergey.senozhatsky@gmail.com

-------------------------------------------------

Petr Mladek (1):
  MAINTAINERS: Add printk maintainers

Sergey Senozhatsky (9):
  printk: use vprintk_func in vprintk()
  printk: rename nmi.c and exported api
  printk: introduce per-cpu safe_print seq buffer
  printk: always use deferred printk when flush printk_safe lines
  printk: report lost messages in printk safe/nmi contexts
  printk: use printk_safe buffers in printk
  printk: remove zap_locks() function
  printk: convert the rest to printk-safe
  printk: drop call_console_drivers() unused param

 MAINTAINERS                 |   8 +
 include/linux/printk.h      |  21 ++-
 init/Kconfig                |  16 +-
 init/main.c                 |   2 +-
 kernel/kexec_core.c         |   2 +-
 kernel/panic.c              |   4 +-
 kernel/printk/Makefile      |   2 +-
 kernel/printk/internal.h    |  79 +++++----
 kernel/printk/nmi.c         | 291 ---------------------------------
 kernel/printk/printk.c      | 232 ++++++++++++--------------
 kernel/printk/printk_safe.c | 385 ++++++++++++++++++++++++++++++++++++++++++++
 lib/nmi_backtrace.c         |   2 +-
 12 files changed, 568 insertions(+), 476 deletions(-)
 delete mode 100644 kernel/printk/nmi.c
 create mode 100644 kernel/printk/printk_safe.c


Best Regards,
Petr Mladek

             reply	other threads:[~2017-02-22 11:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 11:47 Petr Mladek [this message]
2017-02-23  1:39 ` [GIT PULL] printk for 4.11 Linus Torvalds

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=20170222114705.GA30336@linux.suse \
    --to=pmladek@suse.com \
    --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