From: Andrew Morton <akpm@linux-foundation.org>
To: atomlin@redhat.com
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, oleg@redhat.com,
riel@redhat.com
Subject: Re: [RFC PATCH v2 0/2] hung_task: Display every hung task warning
Date: Tue, 14 Jan 2014 16:09:57 -0800 [thread overview]
Message-ID: <20140114160957.949dc28b1d766598792c2ba8@linux-foundation.org> (raw)
In-Reply-To: <1389742918-32598-1-git-send-email-atomlin@redhat.com>
On Tue, 14 Jan 2014 23:41:56 +0000 atomlin@redhat.com wrote:
> The khungtaskd thread limits how many hung task warnings it displays
> at a time, when a timeout occurs. This patch allows that limit to be
> set to "unlimited", by setting hung_task_warnings to -1, which will
> cause khungtaskd to display information about all hung tasks.
The changelog provides no reason why you think this change should be
made. This is awkward, because it means that nobody has any reason
to apply the patch!
prev parent reply other threads:[~2014-01-15 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 23:41 [RFC PATCH v2 0/2] hung_task: Display every hung task warning atomlin
2014-01-14 23:41 ` [RFC PATCH v2 1/2] sysctl: Make neg_one a standard constraint atomlin
2014-01-14 23:41 ` [RFC PATCH v2 2/2] hung_task: Display every hung task warning atomlin
2014-01-15 0:09 ` Andrew Morton [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=20140114160957.949dc28b1d766598792c2ba8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=riel@redhat.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