From: Tejun Heo <tj@kernel.org>
To: Michael Bringmann <mwb@linux.vnet.ibm.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org, nfont@linux.vnet.ibm.com
Subject: Re: [PATCH v7] workqueue: Fix edge cases for calc of pool's cpumask
Date: Fri, 28 Jul 2017 11:08:28 -0400 [thread overview]
Message-ID: <20170728150828.GM742618@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <1f06a3f5-ddb6-ee3f-3496-12e081452232@linux.vnet.ibm.com>
On Thu, Jul 27, 2017 at 04:27:14PM -0500, Michael Bringmann wrote:
>
> There is an underlying assumption/trade-off in many layers of the Linux
> system that CPU <-> node mapping is static. This is despite the presence
> of features like NUMA and 'hotplug' that support the dynamic addition/
> removal of fundamental system resources like CPUs and memory. PowerPC
> systems, however, do provide extensive features for the dynamic change
> of resources available to a system.
>
> Currently, there is little or no synchronization protection around the
> updating of the CPU <-> node mapping, and the export/update of this
> information for other layers / modules. In systems which can change
> this mapping during 'hotplug', like PowerPC, the information is changing
> underneath all layers that might reference it.
>
> This patch attempts to ensure that a valid, usable cpumask attribute is
> used by the workqueue infrastructure when setting up new resource pools.
> It prevents a crash that has been observed when an 'empty' cpumask is
> passed along to the worker/task scheduling code. It is intended as an
> intermediate fix until a more fundamental review and correction of the
> issue can be done.
>
> [With additions to the patch provided by Tejun Hao <tj@kernel.org>]
>
> Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
Applied to wq/for-4.13-fixes with "fix" replaced with "workaround".
Thanks.
--
tejun
prev parent reply other threads:[~2017-07-28 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 21:27 Michael Bringmann
2017-07-28 15:08 ` 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=20170728150828.GM742618@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mwb@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.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
Powered by JetHome