From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: "Liu, Chuansheng" <chuansheng.liu@intel.com>
Cc: Petr Mladek <pmladek@suse.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"sergey.senozhatsky@gmail.com" <sergey.senozhatsky@gmail.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"dvyukov@google.com" <dvyukov@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] kernel/hung_task.c: Force console verbose before panic
Date: Thu, 13 Dec 2018 21:40:54 +0900 [thread overview]
Message-ID: <20181213124054.GA3053@tigerII.localdomain> (raw)
In-Reply-To: <27240C0AC20F114CBF8149A2696CBE4A6015B675@SHSMSX101.ccr.corp.intel.com>
On (12/13/18 01:51), Liu, Chuansheng wrote:
> V1: console_verbose() is used instead of ignore_loglevel,
> suggested by Sergey.
> Tweak the function check_hung_task() suggested by
> Tetsuo to make code more readable.
>
> V2: Petr suggests to make 2 patches:
> One is addressing console_verbose() only, which is
> this patch's aim.
> The other is about forcing sched_show_task() during
> panic, which needs more discussion yet.
>
> Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
> Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
> Cc: Petr Mladek <pmladek@suse.com>
> Signed-off-by: Chuansheng Liu <chuansheng.liu@intel.com>
Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
-ss
prev parent reply other threads:[~2018-12-13 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 1:51 [PATCH V2] kernel/hung_task.c: Force console verbose before panic Liu, Chuansheng
2018-12-13 11:54 ` Petr Mladek
2018-12-13 12:40 ` Sergey Senozhatsky [this message]
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=20181213124054.GA3053@tigerII.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chuansheng.liu@intel.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
/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).