stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Satoru Takeuchi <satoru.takeuchi@gmail.com>
To: Liu hua <sdu.liu@huawei.com>
Cc: Satoru Takeuchi <satoru.takeuchi@gmail.com>,
	<paul.gortmaker@windriver.com>, <mingo@kernel.org>,
	<wangnan0@huawei.com>, <linux-kernel@vger.kernel.org>,
	<peifeiyue@huawei.com>, <lizefan@huawei.com>,
	<stable@vger.kernel.org>
Subject: Re: [PATCH v2] hung_task : check the value of "sysctl_hung_task_timeout_sec"
Date: Fri, 28 Mar 2014 20:56:25 +0900	[thread overview]
Message-ID: <871txmh6za.wl%satoru.takeuchi@gmail.com> (raw)
In-Reply-To: <5332884A.8030904@huawei.com>

Hi Liu,

At Wed, 26 Mar 2014 15:56:58 +0800,
Liu hua wrote:
> 
> 于 2014/3/26 0:25, Satoru Takeuchi 写道:
> > At Tue, 25 Mar 2014 16:58:58 +0800,
> > Liu hua wrote:
> >>
> >> 于 2014/3/24 4:50, Satoru Takeuchi 写道:
> >>> At Sun, 23 Mar 2014 15:54:04 +0800,
> >>> Liu Hua wrote:
> >>>>
> >>>> As sysctl_hung_task_timeout_sec is unsigned long, when this value is
> >>>> larger then LONG_MAX/HZ, the function schedule_timeout_interruptible in
> >>>> watchdog will return immediately without sleep and with print :
> >>>>
> >>>> [  205.452934] schedule_timeout: wrong timeout value ffffffffffffff83
> >>>>
> >>>> and then the funtion watchdog will call schedule_timeout_interruptible again
> >>>> and again. The screen will be filled with
> >>>> 	"schedule_timeout: wrong timeout value ffffffffffffff83"
> >>>>
> >>>> This patch does some check and correction in timeout_jiffies, to let the
> >>>> function schedule_timeout_interruptible allways get the valid parameter.
> >>>>
> >>>> Cc: <stable@vger.kernel.org>
> >>>> Signed-off-by: Liu Hua <sdu.liu@huawei.com>
> >>>> ---
> >>>>  kernel/hung_task.c | 8 ++++++--
> >>>>  1 file changed, 6 insertions(+), 2 deletions(-)
> >>>>
> >>>> diff --git a/kernel/hung_task.c b/kernel/hung_task.c
> >>>> index 6df6149..f992286 100644
> >>>> --- a/kernel/hung_task.c
> >>>> +++ b/kernel/hung_task.c
> >>>> @@ -174,8 +174,12 @@ static void check_hung_uninterruptible_tasks(unsigned long timeout)
> >>>>  
> >>>>  static unsigned long timeout_jiffies(unsigned long timeout)
> >>>>  {
> >>>> -	/* timeout of 0 will disable the watchdog */
> >>>> -	return timeout ? timeout * HZ : MAX_SCHEDULE_TIMEOUT;
> >>>> +	/* timeout of 0 or >= LONG_MAX/HZ will disable the watchdog */
> >>>> +	if ((timeout == 0) || (timeout > MAX_SCHEDULE_TIMEOUT))
> >>>
> >>> You should check whether sysctl_hung_task_timeout_sec > MAX_SCHEDULE_TIMEOUT/HZ
> >>> or not when setting this parameter instead. Then this check ins't necessary here.
> >>>
> >>> # Just FYI, MAX_SCHEDULE_TIMEOUT should be MAX_SCHEDULE_TIMEOUT/HZ here. 
> >>>
> >>> Thanks,
> >>> Satoru
> >>
> >>  Yes, how about this :
> > 
> > I confirmed the followings.
> > 
> >  - 3.14-rc8: system hunged up with "hung_task_timeout_secs > LONG_MAX/HZ".
> >  - 3.14-rc8 with your patch: works fine. I can't set the above mentioned value any more.
> > 
> > Writing possible values (0..LONG_MAX/HZ) in Documentation/sysctl/kernel.txt
> > make this patch better.
> > 
> > Thanks,
> > Satoru
> 
> Thanks to you attention and suggestion. I remade this patch as following.
> Is it appropriate to be reposted with tag "PATCH v3"
> 
> Subject: [PATCH v3] hung_task : check the value of "sysctl_hung_task_timeout_sec"

It looks good to me.

Thanks,
Satoru

> 
> As sysctl_hung_task_timeout_sec is unsigned long, when this value is
> larger then LONG_MAX/HZ, the function schedule_timeout_interruptible in
> watchdog will return immediately without sleep and with print :
> 
> [  205.452934] schedule_timeout: wrong timeout value ffffffffffffff83
> 
> and then the funtion watchdog will call schedule_timeout_interruptible
> again and again. The screen will be filled with
> 	"schedule_timeout: wrong timeout value ffffffffffffff83"
> 
> This patch does some check and correction in sysctl, to let the
> function schedule_timeout_interruptible allways get the valid parameter.
> 
> Signed-off-by: Liu Hua <sdu.liu@huawei.com>
> Tested-by: Satoru Takeuchi <satoru.takeuchi@gmail.com>
> ---
>  Documentation/sysctl/kernel.txt | 1 +
>  kernel/sysctl.c                 | 6 ++++++
>  2 files changed, 7 insertions(+)
> 
> diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
> index e55124e..855d9b3 100644
> --- a/Documentation/sysctl/kernel.txt
> +++ b/Documentation/sysctl/kernel.txt
> @@ -317,6 +317,7 @@ for more than this value report a warning.
>  This file shows up if CONFIG_DETECT_HUNG_TASK is enabled.
> 
>  0: means infinite timeout - no checking done.
> +Possible values to set are in range {0..LONG_MAX/HZ}.
> 
>  ==============================================================
> 
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index 49e13e1..aae21e8 100644
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@ -144,6 +144,11 @@ static int min_percpu_pagelist_fract = 8;
>  static int ngroups_max = NGROUPS_MAX;
>  static const int cap_last_cap = CAP_LAST_CAP;
> 
> +/*this is needed for proc_doulongvec_minmax of sysctl_hung_task_timeout_secs */
> +#ifdef CONFIG_DETECT_HUNG_TASK
> +static unsigned long hung_task_timeout_max = (LONG_MAX/HZ);
> +#endif
> +
>  #ifdef CONFIG_INOTIFY_USER
>  #include <linux/inotify.h>
>  #endif
> @@ -995,6 +1000,7 @@ static struct ctl_table kern_table[] = {
>  		.maxlen		= sizeof(unsigned long),
>  		.mode		= 0644,
>  		.proc_handler	= proc_dohung_task_timeout_secs,
> +		.extra2		= &hung_task_timeout_max,
>  	},
>  	{
>  		.procname	= "hung_task_warnings",
> -- 
> 1.9.0
> 
> Thanks,
> Liu Hua
> 

      reply	other threads:[~2014-03-28 11:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-23  7:54 [PATCH v2] hung_task : check the value of "sysctl_hung_task_timeout_sec" Liu Hua
2014-03-23 20:50 ` Satoru Takeuchi
2014-03-25  8:58   ` Liu hua
2014-03-25 16:25     ` Satoru Takeuchi
2014-03-26  7:56       ` Liu hua
2014-03-28 11:56         ` Satoru Takeuchi [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=871txmh6za.wl%satoru.takeuchi@gmail.com \
    --to=satoru.takeuchi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=mingo@kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=peifeiyue@huawei.com \
    --cc=sdu.liu@huawei.com \
    --cc=stable@vger.kernel.org \
    --cc=wangnan0@huawei.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).