From: tip-bot for Sasha Levin <levinsasha928@gmail.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, levinsasha928@gmail.com,
hpa@zytor.com, mingo@kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, tglx@linutronix.de
Subject: [tip:core/locking] hung task debugging: Inject NMI when hung and going to panic
Date: Wed, 25 Apr 2012 06:53:19 -0700 [thread overview]
Message-ID: <tip-625056b65ee9a8b4caf42136e0c844c15e6ec54f@git.kernel.org> (raw)
In-Reply-To: <1331848040-1676-1-git-send-email-levinsasha928@gmail.com>
Commit-ID: 625056b65ee9a8b4caf42136e0c844c15e6ec54f
Gitweb: http://git.kernel.org/tip/625056b65ee9a8b4caf42136e0c844c15e6ec54f
Author: Sasha Levin <levinsasha928@gmail.com>
AuthorDate: Thu, 15 Mar 2012 17:47:20 -0400
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Wed, 25 Apr 2012 12:39:25 +0200
hung task debugging: Inject NMI when hung and going to panic
Send an NMI to all CPUs when a hung task is detected and the hung
task code is configured to panic. This gives us a fairly uptodate
snapshot of all CPUs in the system.
This lets us get stack trace of all CPUs which makes life easier
trying to debug a deadlock, and the NMI doesn't change anything
since the next step is a kernel panic.
Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Link: http://lkml.kernel.org/r/1331848040-1676-1-git-send-email-levinsasha928@gmail.com
[ extended the changelog a bit ]
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
kernel/hung_task.c | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/kernel/hung_task.c b/kernel/hung_task.c
index c21449f..6df6149 100644
--- a/kernel/hung_task.c
+++ b/kernel/hung_task.c
@@ -108,8 +108,10 @@ static void check_hung_task(struct task_struct *t, unsigned long timeout)
touch_nmi_watchdog();
- if (sysctl_hung_task_panic)
+ if (sysctl_hung_task_panic) {
+ trigger_all_cpu_backtrace();
panic("hung_task: blocked tasks");
+ }
}
/*
prev parent reply other threads:[~2012-04-25 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 21:47 [PATCH] hung task: " Sasha Levin
2012-04-25 13:53 ` tip-bot for Sasha Levin [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=tip-625056b65ee9a8b4caf42136e0c844c15e6ec54f@git.kernel.org \
--to=levinsasha928@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®