From: Andrew Morton <akpm@osdl.org>
To: vatsa@in.ibm.com
Cc: rusty@rustcorp.com.au, mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix deadlock in __create_workqueue
Date: Fri, 30 Apr 2004 19:19:01 -0700 [thread overview]
Message-ID: <20040430191901.510ae947.akpm@osdl.org> (raw)
In-Reply-To: <20040430113751.GA18296@in.ibm.com>
Srivatsa Vaddagiri <vatsa@in.ibm.com> wrote:
>
> Noticed a possible deadlock in __create_workqueue when CONFIG_HOTPLUG_CPU is
> set. This can happen when create_workqueue_thread fails to create a worker
> thread. In that case, we call destroy_workqueue with cpu hotplug lock held.
> destroy_workqueue however also attempts to take the same lock.
>
> Patch below address this deadlock as well as a kthread_stop race.
Fixing a kthread_stop() race is a quite different thing from fixing a
create-workqueue() error-path deadlock and hence should be a separate
patch.
And the description of that separate patch should explain the race which
it is fixing! Yes, the logic in worker_thread() is a bit dorky, but I
don't believe that there is a race in there.
I dropped that part of your patch. Please resend, with justification, if
you disagree.
Thanks.
next prev parent reply other threads:[~2004-05-01 2:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 11:37 Srivatsa Vaddagiri
2004-05-01 2:19 ` Andrew Morton [this message]
2004-05-03 12:24 ` Srivatsa Vaddagiri
2004-05-03 20:08 ` Andrew Morton
2004-05-04 6:51 ` Srivatsa Vaddagiri
2004-05-01 2:27 ` Andrew Morton
2004-05-03 12:23 ` Srivatsa Vaddagiri
2004-05-03 19:25 ` Andrew Morton
2004-05-04 6:50 ` Srivatsa Vaddagiri
2004-05-04 7:35 ` Andrew Morton
2004-05-05 8:37 ` Rusty Russell
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=20040430191901.510ae947.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=vatsa@in.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
all inboxes | Powered by JetHome®