[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87fru19i3x.ffs@tglx>
Date: Wed, 29 May 2024 09:45:22 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Tony W Wang-oc <TonyWWang-oc@...oxin.com>, Dave Hansen
<dave.hansen@...el.com>, 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, 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, Linus
Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] x86/hpet: Read HPET directly if panic in progress
On Wed, May 29 2024 at 14:44, Tony W Wang-oc wrote:
> Actually, this scenario is what this patch is trying to solve.
>
> We encountered hpet_lock deadlock from the call path of the MCE handler,
> and this hpet_lock deadlock scenario may happen when others exceptions'
> handler like #PF/#GP... to call the panic. So read_hpet should avoid
> deadlock if panic in progress.
That's not what your changelog says.
Powered by blists - more mailing lists