public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: atomlin@redhat.com
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, oleg@redhat.com, riel@redhat.com,
	akpm@linux-foundation.org
Subject: [RFC PATCH v3 0/2] hung_task: Display every hung task warning
Date: Wed, 15 Jan 2014 16:27:09 +0000	[thread overview]
Message-ID: <1389803231-16092-1-git-send-email-atomlin@redhat.com> (raw)

From: Aaron Tomlin <atomlin@redhat.com>

When khungtaskd detects hung tasks, it prints out
backtraces from a number of those tasks. Sometimes
the information on why things are stuck is hidden
in those backtraces. Limiting the number of
backtraces being printed out can result in the user
not seeing the information necessary to debug the
issue. This patch introduces an option to print an
unlimited number of backtraces when khungtaskd
detects hung tasks.

While ULONG_MAX is practically "inf", this patch
takes it one step further.  Note: The maximum is
now 2^31-1 (INT_MAX) which should hopefully be
sufficient.

Rebased against v3.13-rc8.

Aaron Tomlin (2):
  sysctl: Make neg_one a standard constraint
  hung_task: Display every hung task warning

 include/linux/sched/sysctl.h | 2 +-
 kernel/hung_task.c           | 6 ++++--
 kernel/sysctl.c              | 6 ++++--
 3 files changed, 9 insertions(+), 5 deletions(-)

-- 
1.8.4.2


             reply	other threads:[~2014-01-15 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 16:27 atomlin [this message]
2014-01-15 16:27 ` [RFC PATCH v3 1/2] sysctl: Make neg_one a standard constraint atomlin
2014-01-15 16:27 ` [RFC PATCH v3 2/2] hung_task: Display every hung task warning atomlin
2014-01-15 20:56   ` David Rientjes

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=1389803231-16092-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=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