[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240528063836.5248-1-TonyWWang-oc@zhaoxin.com>
Date: Tue, 28 May 2024 14:38:36 +0800
From: Tony W Wang-oc <TonyWWang-oc@...oxin.com>
To: <tglx@...utronix.de>, <mingo@...hat.com>, <bp@...en8.de>,
<dave.hansen@...ux.intel.com>, <x86@...nel.org>, <hpa@...or.com>,
<keescook@...omium.org>, <tony.luck@...el.com>, <gpiccoli@...lia.com>,
<mat.jonczyk@...pl>, <rdunlap@...radead.org>,
<alexandre.belloni@...tlin.com>, <mario.limonciello@....com>,
<TonyWWang-oc@...oxin.com>, <yaolu@...inos.cn>, <bhelgaas@...gle.com>,
<justinstitt@...gle.com>, <linux-kernel@...r.kernel.org>,
<linux-hardening@...r.kernel.org>
CC: <CobeChen@...oxin.com>, <TimGuo@...oxin.com>, <LeoLiu-oc@...oxin.com>
Subject: [PATCH] x86/hpet: Read HPET directly if panic in progress
When the clocksource of the system is HPET,a CPU executing read_hpet
might be interrupted by exceptions to executing the panic,this may
lead to read_hpet dead loops:
CPU x CPU x
---- ----
read_hpet()
arch_spin_trylock(&hpet.lock)
[CPU x got the hpet.lock] #MCE happened
do_machine_check()
mce_panic()
panic()
kmsg_dump()
pstore_dump()
pstore_record_init()
ktime_get_real_fast_ns()
read_hpet()
[dead loops]
To avoid this dead loops, read HPET directly if panic in progress.
Signed-off-by: Tony W Wang-oc <TonyWWang-oc@...oxin.com>
---
arch/x86/kernel/hpet.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
index c96ae8fee95e..ecadd0698d6a 100644
--- a/arch/x86/kernel/hpet.c
+++ b/arch/x86/kernel/hpet.c
@@ -804,6 +804,12 @@ static u64 read_hpet(struct clocksource *cs)
if (in_nmi())
return (u64)hpet_readl(HPET_COUNTER);
+ /*
+ * Read HPET directly if panic in progress.
+ */
+ if (unlikely(atomic_read(&panic_cpu) != PANIC_CPU_INVALID))
+ return (u64)hpet_readl(HPET_COUNTER);
+
/*
* Read the current state of the lock and HPET value atomically.
*/
--
2.25.1
Powered by blists - more mailing lists