mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wang Jinchao <wangjinchao600@gmail.com>
To: Petr Mladek <pmladek@suse.com>,
	John Ogness <john.ogness@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Joel Granados <joel.granados@kernel.org>,
	Dave Jiang <dave.jiang@intel.com>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Sravan Kumar Gundu <sravankumarlpu@gmail.com>,
	Ryo Takakura <takakura@valinux.co.jp>
Cc: linux-kernel@vger.kernel.org,
	Wang Jinchao <wangjinchao600@gmail.com>,
	Wei Liu <wei.liu@kernel.org>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: [PATCH] panic: call hardlockup_detector_perf_stop in panic
Date: Wed, 30 Jul 2025 11:06:33 +0800	[thread overview]
Message-ID: <20250730030638.65355-1-wangjinchao600@gmail.com> (raw)

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@gmail.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


             reply	other threads:[~2025-07-30  3:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30  3:06 Wang Jinchao [this message]
2025-08-19 15:01 ` Petr Mladek
2025-08-20  6:22   ` Jinchao Wang
2025-08-20 10:22     ` Petr Mladek
2025-08-21  1:35       ` Jinchao Wang

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=20250730030638.65355-1-wangjinchao600@gmail.com \
    --to=wangjinchao600@gmail.com \
    --cc=dave.jiang@intel.com \
    --cc=jgg@ziepe.ca \
    --cc=joel.granados@kernel.org \
    --cc=john.ogness@linutronix.de \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=sravankumarlpu@gmail.com \
    --cc=takakura@valinux.co.jp \
    --cc=tglx@linutronix.de \
    --cc=wei.liu@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®