[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181210054622.GA6291@jagdpanzerIV>
Date: Mon, 10 Dec 2018 14:46:22 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: "Liu, Chuansheng" <chuansheng.liu@...el.com>
Cc: "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"pmladek@...e.com" <pmladek@...e.com>,
"sergey.senozhatsky@...il.com" <sergey.senozhatsky@...il.com>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"dvyukov@...gle.com" <dvyukov@...gle.com>,
"penguin-kernel@...ove.SAKURA.ne.jp"
<penguin-kernel@...ove.sakura.ne.jp>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kernel/hung_task.c: force ignore_loglevel before panic
On (12/10/18 05:40), Liu, Chuansheng wrote:
> @@ -130,6 +130,13 @@ static void check_hung_task(struct task_struct *t, unsigned long timeout)
> init_utsname()->version);
> pr_err("\"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\""
> " disables this message.\n");
> + /* When sysctl_hung_task_panic is set, we have to force
> + * ignore_loglevel to get really useful hung task
> + * information.
> + */
> + if (sysctl_hung_task_panic && !ignore_loglevel)
> + ignore_loglevel = true;
console_verbose()?
-ss
Powered by blists - more mailing lists