[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <276c9e6b-d647-6f7f-7bd1-c1f45ca23261@huawei.com>
Date: Fri, 30 Dec 2022 09:56:44 +0800
From: Miaohe Lin <linmiaohe@...wei.com>
To: Borislav Petkov <bp@...en8.de>
CC: "Luck, Tony" <tony.luck@...el.com>,
"x86@...nel.org" <x86@...nel.org>, "hpa@...or.com" <hpa@...or.com>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>
Subject: Re: [PATCH] mce: fix missing stack-dumping in mce_panic()
On 2022/12/29 20:51, Borislav Petkov wrote:
> On Thu, Dec 29, 2022 at 08:33:55PM +0800, Miaohe Lin wrote:
>> I think
>
> You think or you know?
The problem code logic exists since that time.
>
> I'm assuming reverting 6e6f0a1f0fa6 shows the MCE panic?
Yes, that's right.
>
> I guess the original issue that commit was fixing is to save that
> redundant oops message but Tony seems to want to see it now and I'm not
> sure how much we care about 80x50 screens nowadays... :-)
80x50 screens should be really uncommon now. But avoiding redundant oops message
should always save our time. ;)
Thanks,
Miaohe Lin
Powered by blists - more mailing lists