[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <470ffd37-3f65-7ad1-71cb-a1d4547d8afa@huawei.com>
Date: Sat, 10 Dec 2022 10:28:11 +0800
From: Miaohe Lin <linmiaohe@...wei.com>
To: <bp@...en8.de>, <tglx@...utronix.de>, <mingo@...hat.com>,
<dave.hansen@...ux.intel.com>
CC: <x86@...nel.org>, <hpa@...or.com>, <linux-edac@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Tony Luck <tony.luck@...el.com>
Subject: Re: [PATCH] mce: fix missing stack-dumping in mce_panic()
On 2022/12/3 0:37, Miaohe Lin wrote:
> When machine check exception occurs, there is no stack-dumping now in
> mce_panic(). It's because bust_spinlocks(1) is called prematurely so
> oops_in_progress will be >= 2 when trying to call dump_stack() in
> panic(). Thus dump_stack() won't be called as this is considered as
> nested stack-dumping.
>
> Signed-off-by: Miaohe Lin <linmiaohe@...wei.com>
Friendly ping. ;)
> ---
> arch/x86/kernel/cpu/mce/core.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/x86/kernel/cpu/mce/core.c b/arch/x86/kernel/cpu/mce/core.c
> index 2c8ec5c71712..c40dad1a6749 100644
> --- a/arch/x86/kernel/cpu/mce/core.c
> +++ b/arch/x86/kernel/cpu/mce/core.c
> @@ -254,7 +254,6 @@ static noinstr void mce_panic(const char *msg, struct mce *final, char *exp)
> wait_for_panic();
> barrier();
>
> - bust_spinlocks(1);
> console_verbose();
> } else {
> /* Don't log too much for fake panic */
>
Powered by blists - more mailing lists