From: Tejun Heo <tj@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Michael Bringmann <mwb@linux.vnet.ibm.com>,
Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+4d497898effeb1936245@syzkaller.appspotmail.com>,
Lai Jiangshan <jiangshanlai@gmail.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: Wed, 24 Jul 2019 10:43:15 -0700 [thread overview]
Message-ID: <20190724174315.GC569612@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <20190724174129.GE213255@gmail.com>
On Wed, Jul 24, 2019 at 10:41:29AM -0700, Eric Biggers wrote:
> The real boot error "general protection fault in dma_direct_max_mapping_size" is
> fixed in mainline now. I believe that unblocks syzbot testing, since it doesn't
> appear to have been blocked by "WARNING: workqueue cpumask: online intersect >
> possible intersect" by itself.
>
> Anyway: Tejun and Michael, any other ideas for why "WARNING: workqueue cpumask:
> online intersect > possible intersect" is still happening?
That code hasn't changed in years. It gotta be changes in cpumask
initialization ordering or sth like that. The easiest way to find the
culprit would be bisecting. I can't get to it right now. Anyone
interested?
Thanks.
--
tejun
next prev parent reply other threads:[~2019-07-24 17:43 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
2019-07-24 17:41 ` Eric Biggers
2019-07-24 17:43 ` Tejun Heo [this message]
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=20190724174315.GC569612@devbig004.ftw2.facebook.com \
--to=tj@kernel.org \
--cc=dvyukov@google.com \
--cc=ebiggers@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.