[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Sat, 12 Dec 2015 14:08:13 -0700
From: Jeff Merkey <linux.mdb@...il.com>
To: LKML <linux-kernel@...r.kernel.org>
Cc: akpm@...ux-foundation.org, uobergfe@...hat.com, dzickus@...hat.com,
atomlin@...hat.com, cmetcalf@...hip.com, fweisbec@...il.com
Subject: [PATCH 1/1] Fix HARD Lockup Firing off while in debugger
The current touch_nmi_watchdog() function in /kernel/watchdog.c does
not always catch all cases when a processor is spinning in the nmi
handler inside either KGDB, KDB, or MDB. The hrtimer_interrupts_saved
count can still end up matching the previous value in some cases,
resulting in the hard lockup detector tagging processors inside a
debugger and executing a panic. The patch below corrects this
problem. I did not add this to the touch_nmi_function directly
becuase of possible affects on timing issues.
I have tested this patch and it fixes the problem for kernel debuggers
stopping errant hard lockup events when processors are spinning inside
the debugger.
Signed-off-by: Jeff V. Merkey <jeffmerkey@...il.com>
diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index 18f34cf..b682aab 100644
--- a/kernel/watchdog.c
+++ b/kernel/watchdog.c
@@ -283,6 +283,13 @@ static bool is_hardlockup(void)
__this_cpu_write(hrtimer_interrupts_saved, hrint);
return false;
}
+
+void touch_hardlockup_watchdog(void)
+{
+ __this_cpu_write(hrtimer_interrupts_saved, 0);
+}
+EXPORT_SYMBOL_GPL(touch_hardlockup_watchdog);
+
#endif
static int is_softlockup(unsigned long touch_ts)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists