[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aQCpLifOIy1Ct4tL@li-276bd24c-2dcc-11b2-a85c-945b6f05615c.ibm.com>
Date: Tue, 28 Oct 2025 12:29:50 +0100
From: Jan Polensky <japo@...ux.ibm.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com, linux-kernel@...r.kernel.org,
x86@...nel.org, Juri Lelli <juri.lelli@...hat.com>,
Tejun Heo <tj@...nel.org>,
Vincent Guittot <vincent.guittot@...aro.org>, cgroups@...r.kernel.org,
aubrey.li@...ux.intel.com, yu.c.chen@...el.com
Subject: Re: [tip:sched/core] [sched] b079d93796:
WARNING:possible_recursive_locking_detected_migration_is_trying_to_acquire_lock:at:set_cpus_allowed_force_but_task_is_already_holding_lock:at:cpu_stopper_thread
On Tue, Oct 28, 2025 at 10:03:24AM +0100, Peter Zijlstra wrote:
> On Mon, Oct 27, 2025 at 12:01:33PM +0100, Peter Zijlstra wrote:
>
> Could someone confirm this fixes the problem?
>
Tested-by: Jan Polensky <japo@...ux.ibm.com>
Thank you for the quick fix. I’ve verified the patch on s390x and can confirm that it resolves the
spin lock issue.
Powered by blists - more mailing lists