[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20250730030638.65355-1-wangjinchao600@gmail.com>
Date: Wed, 30 Jul 2025 11:06:33 +0800
From: Wang Jinchao <wangjinchao600@...il.com>
To: Petr Mladek <pmladek@...e.com>,
John Ogness <john.ogness@...utronix.de>,
Thomas Gleixner <tglx@...utronix.de>,
Joel Granados <joel.granados@...nel.org>,
Dave Jiang <dave.jiang@...el.com>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Sravan Kumar Gundu <sravankumarlpu@...il.com>,
Ryo Takakura <takakura@...inux.co.jp>
Cc: linux-kernel@...r.kernel.org,
Wang Jinchao <wangjinchao600@...il.com>,
Wei Liu <wei.liu@...nel.org>,
Jason Gunthorpe <jgg@...pe.ca>
Subject: [PATCH] panic: call hardlockup_detector_perf_stop in panic
When a panic happens, it blocks the cpu, which may
trigger the hardlockup detector if some dump is slow.
So call hardlockup_detector_perf_stop() to disable
hardlockup dector.
Signed-off-by: Wang Jinchao <wangjinchao600@...il.com>
---
kernel/panic.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/panic.c b/kernel/panic.c
index b0b9a8bf4560..52a1ac4ad447 100644
--- a/kernel/panic.c
+++ b/kernel/panic.c
@@ -339,6 +339,7 @@ void panic(const char *fmt, ...)
*/
local_irq_disable();
preempt_disable_notrace();
+ hardlockup_detector_perf_stop();
/*
* It's possible to come here directly from a panic-assertion and
--
2.43.0
Powered by blists - more mailing lists