From: Andrew Morton <akpm@linux-foundation.org>
To: Josh Hunt <johunt@akamai.com>
Cc: linux-kernel@vger.kernel.org, jbaron@akamai.com
Subject: Re: [PATCH] panic: add TAINT_SOFTLOCKUP
Date: Mon, 23 Jun 2014 15:11:21 -0700 [thread overview]
Message-ID: <20140623151121.44f17779004e94ab620b837c@linux-foundation.org> (raw)
In-Reply-To: <1401847955-3345-1-git-send-email-johunt@akamai.com>
On Tue, 3 Jun 2014 22:12:35 -0400 Josh Hunt <johunt@akamai.com> wrote:
> This taint flag will be set if the system has ever entered a softlockup
> state. Similar to TAINT_WARN it is useful to know whether or not the system
> has been in a softlockup state when debugging.
>
> ...
>
> @@ -329,6 +329,7 @@ static enum hrtimer_restart watchdog_timer_fn(struct hrtimer *hrtimer)
>
> if (softlockup_panic)
> panic("softlockup: hung tasks");
> + add_taint(TAINT_SOFTLOCKUP, LOCKDEP_STILL_OK);
> __this_cpu_write(soft_watchdog_warn, true);
> } else
> __this_cpu_write(soft_watchdog_warn, false);
Would make more sense to have applied the taint *before* calling
panic()?
diff -puN kernel/watchdog.c~panic-add-taint_softlockup-fix kernel/watchdog.c
--- a/kernel/watchdog.c~panic-add-taint_softlockup-fix
+++ a/kernel/watchdog.c
@@ -368,9 +368,9 @@ static enum hrtimer_restart watchdog_tim
smp_mb__after_atomic();
}
+ add_taint(TAINT_SOFTLOCKUP, LOCKDEP_STILL_OK);
if (softlockup_panic)
panic("softlockup: hung tasks");
- add_taint(TAINT_SOFTLOCKUP, LOCKDEP_STILL_OK);
__this_cpu_write(soft_watchdog_warn, true);
} else
__this_cpu_write(soft_watchdog_warn, false);
next prev parent reply other threads:[~2014-06-23 22:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 2:12 Josh Hunt
2014-06-23 22:11 ` Andrew Morton [this message]
2014-06-23 22:45 ` Josh Hunt
2014-06-23 22:51 ` Andrew Morton
2014-06-24 14:22 ` Josh Hunt
2014-06-24 15:06 ` Dave Jones
2014-06-24 15:20 ` Dave Jones
2014-06-25 0:45 ` David Rientjes
[not found] ` <CAPDOMVifbWCohymLyCc6cxG7t9WCDLTbCWRZx8xyG3DOMFqKqg@mail.gmail.com>
2014-06-25 2:21 ` Nick Krause
2014-06-25 3:24 ` Josh Hunt
2014-06-25 3:39 ` Nick Krause
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=20140623151121.44f17779004e94ab620b837c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jbaron@akamai.com \
--cc=johunt@akamai.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®