Messages in this thread |  | | Date | Mon, 20 Nov 2023 09:07:34 -1000 | From | Tejun Heo <> | Subject | Re: [PATCH] workqueue: fix invalid cpu in kick_pool |
| |
Hello,
On Mon, Nov 20, 2023 at 08:16:23PM +0800, Yong He wrote: > With incorrect unbound workqueue configurations, this may introduce kernel > panic, because cpumask_any_distribute() will not always return a valid cpu, > such as one set the 'isolcpus' and 'workqueue.unbound_cpus' into the same > cpuset, and this will make the @pool->attrs->__pod_cpumask an empty set, > then trigger panic like this:
This shouldn't have happened. Can you share the configuration and the full dmesg? Let's fix the problem at the source.
Thanks.
-- tejun
|  |