From: Tejun Heo <tj@kernel.org>
To: Eryu Guan <eguan@redhat.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Balbir Singh <bsingharora@gmail.com>,
liwan@redhat.com,
"open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
<linuxppc-dev@lists.ozlabs.org>
Subject: Re: kworker with empty task->cpus_allowed (was Re: [v4.12-rc1 regression] mount ext4 fs results in kernel crash on PPC64le host)
Date: Thu, 29 Jun 2017 10:24:25 -0400 [thread overview]
Message-ID: <20170629142425.GB3531@htj.duckdns.org> (raw)
In-Reply-To: <20170629135919.GU23360@eguan.usersys.redhat.com>
Hello,
Could be the same problem as the one reported in the following thread.
http://lkml.kernel.org/r/1497266622.15415.39.camel@abdul.in.ibm.com
The root cause there is ppc arch code not setting up possible cpu <->
numa mapping during boot.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-06-29 14:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 8:32 [v4.12-rc1 regression] mount ext4 fs results in kernel crash on PPC64le host Eryu Guan
2017-06-28 17:16 ` Balbir Singh
2017-06-29 3:41 ` Eryu Guan
2017-06-29 8:47 ` Balbir Singh
2017-06-29 9:04 ` Eryu Guan
2017-06-29 10:05 ` Eryu Guan
2017-06-29 11:12 ` Michael Ellerman
2017-06-29 11:39 ` Eryu Guan
2017-06-29 12:06 ` kworker with empty task->cpus_allowed (was Re: [v4.12-rc1 regression] mount ext4 fs results in kernel crash on PPC64le host) Michael Ellerman
2017-06-29 13:59 ` Eryu Guan
2017-06-29 14:24 ` Tejun Heo [this message]
2017-06-30 1:08 ` Michael Ellerman
2017-06-30 11:56 ` Tejun Heo
2017-06-30 10:07 ` Michael Ellerman
2017-06-30 11:47 ` Eryu Guan
2017-07-04 6:26 ` Michael Ellerman
2017-07-04 8:21 ` Eryu Guan
2017-07-04 11:06 ` Michael Ellerman
2017-07-04 12:12 ` Eryu Guan
2017-06-29 4:54 ` [v4.12-rc1 regression] mount ext4 fs results in kernel crash on PPC64le host Michael Ellerman
2017-06-29 10:27 ` Michael Ellerman
2017-06-29 10:33 ` Eryu Guan
2017-06-29 12:13 ` Michael Ellerman
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=20170629142425.GB3531@htj.duckdns.org \
--to=tj@kernel.org \
--cc=bsingharora@gmail.com \
--cc=eguan@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liwan@redhat.com \
--cc=mpe@ellerman.id.au \
/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).