From: Oleg Nesterov <oleg@tv-sign.ru>
To: Dmitry Adamushko <dmitry.adamushko@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch, minor] workqueue: consistently use 'err' in __create_workqueue_key()
Date: Tue, 29 Jul 2008 15:02:50 +0400 [thread overview]
Message-ID: <20080729110250.GA177@tv-sign.ru> (raw)
In-Reply-To: <1217277694.20627.9.camel@earth>
On 07/28, Dmitry Adamushko wrote:
>
> I guess error handling is a bit illogical in __create_workqueue_key()
Please see below,
> for_each_possible_cpu(cpu) {
> cwq = init_cpu_workqueue(wq, cpu);
> - if (err || !cpu_online(cpu))
> + if (!cpu_online(cpu))
> continue;
> err = create_workqueue_thread(cwq, cpu);
> + if (err)
> + break;
This was done on purpose. The code above does init_cpu_workqueue(cpu)
for each possible cpu, even if we fail to create cwq->thread for some
cpu. This way destroy_workqueue() (called below) shouldn't worry about
the partially initialized workqueues.
The patch above should work, but it assumes that destroy_workqueue()
must do nothing with cwq if cwq->thread == NULL, this is not very
robust.
And, more importantly. Let's suppose __create_workqueue_key() does
"break" and drops cpu_add_remove_lock. Then we race with cpu-hotplug
which can hit the uninitialized cwq. This is fixable, but needs other
complication.
Oleg.
next prev parent reply other threads:[~2008-07-29 10:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 20:41 [patch, minor] workqueue: consistently use 'err' in __create_workqueue_key() Dmitry Adamushko
2008-07-29 11:02 ` Oleg Nesterov [this message]
2008-07-29 11:58 ` Dmitry Adamushko
2008-07-29 12:52 ` Oleg Nesterov
2008-07-29 13:44 ` Oleg Nesterov
2008-07-29 14:20 ` Dmitry Adamushko
2008-07-29 16:13 ` Oleg Nesterov
2008-07-29 16:52 ` Dmitry Adamushko
2008-07-29 16:22 ` [PATCH] workqueues: add comments to __create_workqueue_key() Oleg Nesterov
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=20080729110250.GA177@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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