From: Tony W Wang-oc <TonyWWang-oc@zhaoxin.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Dave Hansen <dave.hansen@intel.com>, <mingo@redhat.com>,
<bp@alien8.de>, <dave.hansen@linux.intel.com>, <x86@kernel.org>,
<hpa@zytor.com>, <keescook@chromium.org>, <tony.luck@intel.com>,
<gpiccoli@igalia.com>, <mat.jonczyk@o2.pl>,
<rdunlap@infradead.org>, <alexandre.belloni@bootlin.com>,
<mario.limonciello@amd.com>, <yaolu@kylinos.cn>,
<bhelgaas@google.com>, <justinstitt@google.com>,
<linux-kernel@vger.kernel.org>, <linux-hardening@vger.kernel.org>
Cc: <CobeChen@zhaoxin.com>, <TimGuo@zhaoxin.com>,
<LeoLiu-oc@zhaoxin.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] x86/hpet: Read HPET directly if panic in progress
Date: Wed, 29 May 2024 16:15:37 +0800 [thread overview]
Message-ID: <d8952567-f97d-45ae-976e-5fe5d172df41@zhaoxin.com> (raw)
In-Reply-To: <87fru19i3x.ffs@tglx>
On 2024/5/29 15:45, Thomas Gleixner wrote:
>
>
> [这封邮件来自外部发件人 谨防风险]
>
> 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.
Yes.
The example flow I gave with the MCE handler in my changelog is misleading.
next prev parent reply other threads:[~2024-05-29 8:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 6:38 Tony W Wang-oc
2024-05-28 14:18 ` Dave Hansen
2024-05-28 22:12 ` Thomas Gleixner
2024-05-28 23:22 ` Linus Torvalds
2024-05-29 7:42 ` Thomas Gleixner
2024-06-05 6:23 ` Tony W Wang-oc
2024-06-05 9:36 ` Borislav Petkov
2024-06-05 10:10 ` Tony W Wang-oc
2024-06-05 11:33 ` Borislav Petkov
2024-06-05 12:02 ` Tony W Wang-oc
2024-06-05 15:51 ` Luck, Tony
2024-06-06 8:44 ` Tony W Wang-oc
2024-06-06 17:00 ` Luck, Tony
2024-05-29 4:39 ` Tony W Wang-oc
2024-05-29 6:44 ` Tony W Wang-oc
2024-05-29 7:45 ` Thomas Gleixner
2024-05-29 8:15 ` Tony W Wang-oc [this message]
2024-05-29 7:44 ` Thomas Gleixner
2024-07-01 11:09 ` Tony W Wang-oc
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=d8952567-f97d-45ae-976e-5fe5d172df41@zhaoxin.com \
--to=tonywwang-oc@zhaoxin.com \
--cc=CobeChen@zhaoxin.com \
--cc=LeoLiu-oc@zhaoxin.com \
--cc=TimGuo@zhaoxin.com \
--cc=alexandre.belloni@bootlin.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gpiccoli@igalia.com \
--cc=hpa@zytor.com \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mat.jonczyk@o2.pl \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yaolu@kylinos.cn \
/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®