From: Tejun Heo <theo@redhat.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>, linux-kernel@vger.kernel.org
Cc: Gustavo Luiz Duarte <gduarte@redhat.com>,
Mike Anderson <mike.anderson@us.ibm.com>,
Tomas Henzl <thenzl@redhat.com>
Subject: Re: [PATCH wq/for-3.18] workqueue: apply __WQ_ORDERED to create_singlethread_workqueue()
Date: Sat, 13 Sep 2014 05:12:41 +0900 [thread overview]
Message-ID: <20140912201241.GB23756@mtj.dyndns.org> (raw)
In-Reply-To: <20140912195328.GA23756@mtj.dyndns.org>
On Sat, Sep 13, 2014 at 04:53:28AM +0900, Tejun Heo wrote:
> From e141deffe6a30cfe7dd6ad97f21afa85b80ca3ac Mon Sep 17 00:00:00 2001
> From: Tejun Heo <tj@kernel.org>
> Date: Sat, 13 Sep 2014 04:14:30 +0900
>
> create_singlethread_workqueue() is a compat interface for singled
> threaded workqueue which maps to ordered workqueue w/ rescuer in the
> current implementation. create_singlethread_workqueue() currently
> implemented by invoking alloc_workqueue() w/ appropriate parameters.
>
> 8719dceae2f9 ("workqueue: reject adjusting max_active or applying
> attrs to ordered workqueues") introduced __WQ_ORDERED to protect
> ordered workqueues against dynamic attribute changes which can break
> ordering guarantees but forgot to apply it to
> create_singlethread_workqueue(). While this can be potentially
> dangerous, this isn't a problem in practice given the existing uses of
> dynamic attribute changes.
>
> Let's make create_singlethread_workqueue() wrap
> alloc_ordered_workqueue() instead so that it inherits __WQ_ORDERED and
> can implicitly track future ordered_workqueue changes.
Oops, this is the right change but w/ wrong description and branch.
W/o __WQ_ORDERED, create_singlethread_workqueue() is broken on NUMA
setups. Will respin the patch.
Thanks.
--
tejun
next prev parent reply other threads:[~2014-09-12 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 19:53 Tejun Heo
2014-09-12 20:12 ` Tejun Heo [this message]
2014-09-12 20:24 ` [PATCH v2 wq/for-3.17-fixes] " Tejun Heo
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=20140912201241.GB23756@mtj.dyndns.org \
--to=theo@redhat.com \
--cc=gduarte@redhat.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.anderson@us.ibm.com \
--cc=thenzl@redhat.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
all inboxes | Powered by JetHome®