From: Li Zefan <lizefan@huawei.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hung_task: change sysctl_hung_task_check_count to int
Date: Sat, 14 Sep 2013 14:57:12 +0800 [thread overview]
Message-ID: <523408C8.3040606@huawei.com> (raw)
In-Reply-To: <20130914055359.GB364@gmail.com>
>> On 2013/9/14 10:47, Li Zefan wrote:
>>> As sysctl_hung_task_check_count is unsigned long, when this value is
>>> assigned to max_count in check_hung_uninterruptible_tasks(), it's
>>> truncated to int type.
>>>
>>> Therefore if we write 2^32 to sysctl.hung_task_check_count, hung task
>>> detection will be effectively disabled.
>>>
>>> Not a big deal, but still it's better to fix this inconsistency.
>>>
>>> Signed-off-by: Li Zefan <lizefan@huawei.com>
>>> ---
>>> include/linux/sched/sysctl.h | 2 +-
>>> kernel/hung_task.c | 2 +-
>>> kernel/sysctl.c | 4 ++--
>>> 3 files changed, 4 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/include/linux/sched/sysctl.h b/include/linux/sched/sysctl.h
>>> index bf8086b..9552afa 100644
>>> --- a/include/linux/sched/sysctl.h
>>> +++ b/include/linux/sched/sysctl.h
>>> @@ -2,8 +2,8 @@
>>> #define _SCHED_SYSCTL_H
>>>
>>> #ifdef CONFIG_DETECT_HUNG_TASK
>>> +extern int sysctl_hung_task_check_count;
>>> extern unsigned int sysctl_hung_task_panic;
>>> -extern unsigned long sysctl_hung_task_check_count;
>>> extern unsigned long sysctl_hung_task_timeout_secs; extern unsigned
>>> long sysctl_hung_task_warnings; extern int
>>> proc_dohung_task_timeout_secs(struct ctl_table *table, int write,
>
> Looks good, but I suppose most of the unsigned longs above ought to be
> downgraded to int as well?
>
They can be, but they don't have to be.
> Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks!
prev parent reply other threads:[~2013-09-14 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 2:47 [PATCH] hung_task: change sysctl_hung_task_check_count to int Li Zefan
2013-09-14 2:53 ` Li Zefan
2013-09-14 5:53 ` Ingo Molnar
2013-09-14 6:57 ` Li Zefan [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=523408C8.3040606@huawei.com \
--to=lizefan@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
/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