From: Eric Biggers <ebiggers@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Tejun Heo <tj@kernel.org>,
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, 23 Jul 2019 09:31:27 -0700 [thread overview]
Message-ID: <20190723163126.GB23641@gmail.com> (raw)
In-Reply-To: <CACT4Y+ZNTh=t62oj_Y5XyQwjOJp3AWwWi8c-4DrX+jKNCVqzzg@mail.gmail.com>
On Tue, Jul 23, 2019 at 10:16:24AM +0200, 'Dmitry Vyukov' via syzkaller-bugs wrote:
> On Tue, Jun 11, 2019 at 8:52 PM Tejun Heo <tj@kernel.org> wrote:
> >
> > 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.
>
> This has reached upstream and all subsystem subtrees, now all Linux
> trees are boot broken (except for few that still lack behind):
> https://syzkaller.appspot.com/upstream
>
> No new Linux code is tested by syzbot at this point.
>
AFAICS, what's actually happening is that the boot fails due to a different bug,
"general protection fault in dma_direct_max_mapping_size" -- which is a real
boot error, not just a warning; see
https://lkml.kernel.org/lkml/20190723161425.GA23641@gmail.com/
syzbot then sees "WARNING: workqueue cpumask: online intersect > possible
intersect" in the console output prior to that, and uses that as the bug title.
It's not obvious that syzbot would report "WARNING: workqueue cpumask: online
intersect > possible intersect" without the real boot error too.
Nevertheless the issue is still there and something needs to be done about it.
- Eric
next prev parent reply other threads:[~2019-07-23 16:31 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
2019-07-23 8:16 ` Dmitry Vyukov
2019-07-23 16:31 ` Eric Biggers [this message]
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=20190723163126.GB23641@gmail.com \
--to=ebiggers@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 \
--cc=tj@kernel.org \
/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).