[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aNVIMhQKlBp43iHs@arm.com>
Date: Thu, 25 Sep 2025 14:48:34 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: shechenglong <shechenglong@...sion.com>
Cc: will@...nel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, stone.xulei@...sion.com,
chenjialong@...sion.com, yuxiating@...sion.com,
Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH] cpu: fix hard lockup triggered by printk calls within
scheduling context
On Wed, Sep 24, 2025 at 08:32:47PM +0800, shechenglong wrote:
> relocate the printk() calls from spectre_v4_mitigations_off() and
> spectre_v2_mitigations_off() into setup_system_capabilities() function,
> preventing hard lockups that occur when printk() is invoked from scheduler context.
>
> Link: https://patchwork.kernel.org/project/linux-arm-kernel/patch/20250918064907.1832-1-shechenglong@xfusion.com/
> Suggested-by: Mark Rutland <mark.rutland@....com>
> Suggested-by: Catalin Marinas <catalin.marinas@....com>
> Signed-off-by: shechenglong <shechenglong@...sion.com>
It looks fine to me. Thanks.
Reviewed-by: Catalin Marinas <catalin.marinas@....com>
Will, do you want to take this for 6.18? It might be worth a cc stable.
In general it's unlikely to happen unless you keep writing to
/sys/kernel/debug/clear_warn_once.
--
Catalin
Powered by blists - more mailing lists