From: Aaron Tomlin <atomlin@redhat.com>
To: mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, rientjes@google.com,
mingo@redhat.com, oleg@redhat.com, riel@redhat.com,
akpm@linux-foundation.org, atomlin@redhat.com
Subject: [RFC PATCH v5 0/2] hung_task: Display every hung task warning
Date: Thu, 23 Jan 2014 10:56:01 +0000 [thread overview]
Message-ID: <1390474563-15424-1-git-send-email-atomlin@redhat.com> (raw)
When khungtaskd detects hung tasks, it prints out backtraces from
a number of those tasks. Limiting the number of backtraces being
printed out can result in the user not seeing the information
necessary to debug the issue. The hung_task_warnings sysctl
controls this feature.
This patch makes it possible for hung_task_warnings to accept a
special value to print an unlimited number of backtraces when
khungtaskd detects hung tasks.
The special value is -1. To use this value it is necessary to
change types from ulong to int.
Rebased against v3.13-rc8.
Changes since v4:
- Improve the documentation on hung_task_warnings
Changes since v3:
- Simplify the commit message (Rik van Riel and David Rientjes)
- Document hung_task_* sysctl parameters (David Rientjes)
Aaron Tomlin (2):
sysctl: Make neg_one a standard constraint
hung_task: Display every hung task warning
Documentation/sysctl/kernel.txt | 42 +++++++++++++++++++++++++++++++++++++++++
include/linux/sched/sysctl.h | 2 +-
kernel/hung_task.c | 6 ++++--
kernel/sysctl.c | 6 ++++--
4 files changed, 51 insertions(+), 5 deletions(-)
--
1.8.4.2
next reply other threads:[~2014-01-23 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 10:56 Aaron Tomlin [this message]
2014-01-23 10:56 ` [RFC PATCH v5 1/2] sysctl: Make neg_one a standard constraint Aaron Tomlin
2014-01-25 8:48 ` Ingo Molnar
2014-01-25 8:58 ` Ingo Molnar
2014-01-23 10:56 ` [RFC PATCH v5 2/2] hung_task: Display every hung task warning Aaron Tomlin
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=1390474563-15424-1-git-send-email-atomlin@redhat.com \
--to=atomlin@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=riel@redhat.com \
--cc=rientjes@google.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
Powered by JetHome