From: Tejun Heo <tj@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+4d497898effeb1936245@syzkaller.appspotmail.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
mwb@linux.vnet.ibm.com, LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: linux-next boot error: WARNING: workqueue cpumask: online intersect > possible intersect
Date: Tue, 11 Jun 2019 11:52:06 -0700 [thread overview]
Message-ID: <20190611185206.GG3341036@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <CACT4Y+ZZy5nqduErU8hjKrwThHiybGpwd3QzOviAWftZFZ4d2A@mail.gmail.com>
Hello,
On Fri, Jun 07, 2019 at 10:45:45AM +0200, Dmitry Vyukov wrote:
> +workqueue maintainers and Michael who added this WARNING
>
> The WARNING was added in 2017, so I guess it's a change somewhere else
> that triggered it.
> The WARNING message does not seem to give enough info about the caller
> (should it be changed to WARN_ONCE to print a stack?). How can be root
> cause this and unbreak linux-next?
So, during boot, workqueue builds masks of possible cpus of each node
and stores them on wq_numa_possible_cpumask[] array. The warning is
saying that somehow online cpumask of a node became a superset of the
possible mask, which should never happen.
Dumping all masks in wq_numa_possible_cpumasks[] and cpumask_of_node()
of each node should show what's going on.
Thanks.
--
tejun
next prev parent reply other threads:[~2019-06-11 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 8:33 linux-next boot error: WARNING: workqueue cpumask: online intersect > possible intersect syzbot
2019-06-07 8:45 ` Dmitry Vyukov
2019-06-11 18:52 ` Tejun Heo [this message]
2019-07-23 8:16 ` Dmitry Vyukov
2019-07-23 16:31 ` Eric Biggers
2019-07-24 17:41 ` Eric Biggers
2019-07-24 17:43 ` Tejun Heo
2019-11-08 12:46 ` Dmitry Vyukov
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=20190611185206.GG3341036@devbig004.ftw2.facebook.com \
--to=tj@kernel.org \
--cc=dvyukov@google.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mwb@linux.vnet.ibm.com \
--cc=syzbot+4d497898effeb1936245@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).