From: Liu hua <sdu.liu@huawei.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
Ingo Molnar <mingo@kernel.org>
Cc: <oleg@redhat.com>, Li Zefan <lizefan@huawei.com>,
Wang Nan <wangnan0@huawei.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hung_task : check the value of "sysctl_hung_task_timeout_sec"
Date: Mon, 10 Mar 2014 11:34:22 +0800 [thread overview]
Message-ID: <531D32BE.2090601@huawei.com> (raw)
In-Reply-To: <531895C6.9000305@windriver.com>
on 2014/3/6 23:35, Paul Gortmaker wrote:
> On 14-03-06 02:19 AM, Liu hua wrote:
>> As sysctl_hung_task_timeout_sec is unsigned long, when this value is
>> larger then LONG_MAX, the function schedule_timeout_interruptible in
>> watchdog will return immediately without sleep :
>>
>> for example (in x86_64 platform):
>>
>> linux# echo 0xFFFFFFFFFFFFFFFF > /proc/sys/kernel/hung_task_timeout_secs
>>
>> [ 66.798350] schedule_timeout: wrong timeout value ffffffffffffff06
>> [ 66.800064] schedule_timeout: wrong timeout value ffffffffffffff06
>> [ 66.801774] schedule_timeout: wrong timeout value ffffffffffffff06
>> [ 66.803488] schedule_timeout: wrong timeout value ffffffffffffff06
>> [ 66.805225] schedule_timeout: wrong timeout value ffffffffffffff06
>>
>> The screen was filled with "schedule_timeout: wrong timeout value
>> ffffffffffffff06" and the system stalled.
>>
>> So I do some check and correction in timeout_jiffies, to let the function
>> schedule_timeout_interruptible allways get the valid parameter.
>>
>> Signed-off-by: Liu Hua <sdu.liu@huawei.com>
>> ---
>> kernel/hung_task.c | 11 ++++++++++-
>> 1 file changed, 10 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/hung_task.c b/kernel/hung_task.c
>> index 06bb141..ef96650 100644
>> --- a/kernel/hung_task.c
>> +++ b/kernel/hung_task.c
>> @@ -186,7 +186,16 @@ static void check_hung_uninterruptible_tasks(unsigned long timeout)
>> static unsigned long timeout_jiffies(unsigned long timeout)
>> {
>> /* timeout of 0 will disable the watchdog */
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are breaking the above functionality/feature by declaring
> zero invalid.
>
> Paul.
> --
>
Actually the patch will disable the watchdog if the timeout is illegal(except 0) for
schedule_timeout_interruptible.
I will make a new patch that disables the watchdog when the timeout is 0 or above
LONG_MAX without printing errors ?
What do you think?
Liu Hua
>> - return timeout ? timeout * HZ : MAX_SCHEDULE_TIMEOUT;
>> + if ((timeout == 0) || (timeout > MAX_SCHEDULE_TIMEOUT)) {
>> + pr_err("%s : wrong timeout value %lx\n",
>> + __func__, timeout);
>> + pr_err("Timeout value is set to MAX_SCHEDULE_TIMEOUT(%lx) now.\n",
>> + MAX_SCHEDULE_TIMEOUT);
>> + return MAX_SCHEDULE_TIMEOUT;
>> + }
>> +
>> + return (timeout * HZ) < MAX_SCHEDULE_TIMEOUT ?
>> + timeout * HZ : MAX_SCHEDULE_TIMEOUT;
>> }
>>
>> /*
>>
>
> .
>
prev parent reply other threads:[~2014-03-10 3:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1394089669-18285-1-git-send-email-sdu.liu@huawei.com>
2014-03-06 7:19 ` [PATCH] hung_task : check the value of "sysctl_hung_task_timeout_sec" Liu hua
2014-03-06 15:35 ` Paul Gortmaker
2014-03-10 3:34 ` Liu hua [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=531D32BE.2090601@huawei.com \
--to=sdu.liu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paul.gortmaker@windriver.com \
--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