From: Tejun Heo <tj@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [tj-wq:affinity-scopes-dbg-invalid-cpu] [workqueue] e3485721f9: WARNING:at_kernel/workqueue.c:#workqueue_online_cpu
Date: Mon, 12 Jun 2023 07:43:28 -1000 [thread overview]
Message-ID: <ZIdZQBJbOkuaAYvx@slm.duckdns.org> (raw)
In-Reply-To: <ZIdY8-aOIR3lQI3M@slm.duckdns.org>
On Mon, Jun 12, 2023 at 07:42:11AM -1000, Tejun Heo wrote:
> On Mon, Jun 12, 2023 at 10:04:02AM +0800, kernel test robot wrote:
> > [ 3.388228][ T21] ------------[ cut here ]------------
> > [ 3.394990][ T21] WARNING: CPU: 1 PID: 21 at kernel/workqueue.c:5393 workqueue_online_cpu (kernel/workqueue.c:5393 kernel/workqueue.c:5481)
> ...
> > [ 3.584746][ T21] ? workqueue_prepare_cpu (kernel/workqueue.c:5470)
> > [ 3.591752][ T21] ? local_clock (kernel/sched/clock.c:270 kernel/sched/clock.c:307)
> > [ 3.596749][ T21] cpuhp_invoke_callback (arch/x86/include/asm/jump_label.h:27 include/linux/jump_label.h:207 include/trace/events/cpuhp.h:65 kernel/cpu.c:193)
> > [ 3.603751][ T21] ? try_to_wake_up (include/linux/sched.h:2254 kernel/sched/core.c:4312)
> > [ 3.610751][ T21] cpuhp_thread_fun (kernel/cpu.c:815)
>
> This is set_cpus_allowed_ptr() failing on kworkers when workqueue tries to
> put back the per-cpu kworkers on the onlining CPU, which is rather
> unexpected. Let me include the error code in the warning message so that we
> can understand why it fails the next time.
Ah, never mind. This ->__pod_cpumaks not being initialized correctly by the
patch and is already fixed in the newer version of the code.
Thanks.
--
tejun
prev parent reply other threads:[~2023-06-12 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 2:04 [tj-wq:affinity-scopes-dbg-invalid-cpu] [workqueue] e3485721f9: WARNING:at_kernel/workqueue.c:#workqueue_online_cpu kernel test robot
2023-06-12 17:42 ` Tejun Heo
2023-06-12 17:43 ` Tejun Heo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZIdZQBJbOkuaAYvx@slm.duckdns.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox