All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Feng Tang <feng.tang@intel.com>
Cc: Petr Mladek <pmladek@suse.com>,
	akpm@linux-foundation.org, bp@suse.de, keescook@chromium.org,
	mm-commits@vger.kernel.org, sergey.senozhatsky@gmail.com,
	stable@vger.kernel.org, tglx@linutronix.de,
	Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: + panic-avoid-the-extra-noise-dmesg.patch added to -mm tree
Date: Wed, 5 Dec 2018 11:26:54 +0900	[thread overview]
Message-ID: <20181205022654.GA503@jagdpanzerIV> (raw)
In-Reply-To: <20181204154936.wbgcovzpc54n6dvs@shbuild888>

On (12/04/18 23:49), Feng Tang wrote:
> This should be able to achieve the same goal. 
> 
> One thing I can think of is what mentioned by Sergey that some sysrq
> handler may want to print out something, but it should mostly be
> covered by 2 other panic debug print patches, which will print out
> task/mem/timer/lock/ftrace info runtime on demand.

Well, not all sysrq handlers just printk stuff; some do sane things,
like emergency sync, umount, etc.

	-ss

  parent reply	other threads:[~2018-12-05  2:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04  7:15 + panic-avoid-the-extra-noise-dmesg.patch added to -mm tree akpm
2018-12-04 10:10 ` Sergey Senozhatsky
2018-12-04 10:20 ` Petr Mladek
2018-12-04 15:49   ` Feng Tang
2018-12-04 16:01     ` Petr Mladek
2018-12-05  1:53       ` Feng Tang
2018-12-05  2:50         ` Sergey Senozhatsky
2018-12-05  3:05           ` Sergey Senozhatsky
2018-12-05  3:27             ` Feng Tang
2018-12-05  2:26     ` Sergey Senozhatsky [this message]
2018-12-05  2:47       ` Feng Tang
2018-12-05  2:57         ` Sergey Senozhatsky
2018-12-05  5:29           ` Sergey Senozhatsky
2018-12-05  8:00             ` Sergey Senozhatsky
2018-12-05 15:46               ` Feng Tang
2018-12-06  3:58                 ` Feng Tang
2018-12-07  9:50                   ` Sergey Senozhatsky
2018-12-10  9:45                     ` Feng Tang
2018-12-10 15:57                       ` Petr Mladek
2018-12-11  8:07                         ` Sergey Senozhatsky
2018-12-11  8:22                           ` Petr Mladek
2018-12-11  8:26                             ` Sergey Senozhatsky
2018-12-11  8:32                           ` Feng Tang
2018-12-11  9:08                             ` Sergey Senozhatsky
2018-12-11  8:00                       ` Sergey Senozhatsky

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=20181205022654.GA503@jagdpanzerIV \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=feng.tang@intel.com \
    --cc=keescook@chromium.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=sashal@kernel.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.