From: Oleg Nesterov <oleg@tv-sign.ru>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: + workqueue-proper-error-unwinding-in-cpu-hotplug-error-path.patch added to -mm tree
Date: Tue, 22 Jul 2008 13:16:36 +0400 [thread overview]
Message-ID: <20080722091636.GA241@tv-sign.ru> (raw)
In-Reply-To: <20080722085938.GA5857@localhost.localdomain>
On 07/22, Akinobu Mita wrote:
>
> On Tue, Jul 22, 2008 at 12:45:26PM +0400, Oleg Nesterov wrote:
> > >
> > > From: Akinobu Mita <akinobu.mita@gmail.com>
> > >
> > > --- a/kernel/workqueue.c~workqueue-proper-error-unwinding-in-cpu-hotplug-error-path
> > > +++ a/kernel/workqueue.c
> > > @@ -928,6 +928,15 @@ static int __devinit workqueue_cpu_callb
> > > break;
> > > printk(KERN_ERR "workqueue [%s] for %i failed\n",
> > > wq->name, cpu);
> > > +
> > > + list_for_each_entry_continue_reverse(wq, &workqueues,
> > > + list) {
> > > + cwq = per_cpu_ptr(wq->cpu_wq, cpu);
> > > + start_workqueue_thread(cwq, -1);
> > > + cleanup_workqueue_thread(cwq);
> > > + }
> > > + cpu_clear(cpu, cpu_populated_map);
> > > +
> > > return NOTIFY_BAD;
> >
> > If CPU_UP_PREPARE fails, _cpu_up() sends CPU_UP_CANCELED, and afaics
> > workqueue_cpu_callback() correctly cleanups cwq->thread's.
>
> _cpu_up() does not send CPU_UP_CANCELED to the callback which has
> returned NOTIFY_BAD.
>
> The behavior was changed by this commit:
>
> commit a0d8cdb652d35af9319a9e0fb7134de2a276c636
> Author: Akinobu Mita <akinobu.mita@gmail.com>
> Date: Thu Oct 18 03:05:12 2007 -0700
>
> cpu hotplug: cpu: deliver CPU_UP_CANCELED only to NOTIFY_OKed callbacks with CPU_UP_PREPARE
Thanks Akinobu!
Can't we simplify the fix? I don't like the fact that the CPU_UP_CANCELED
logic is duplicated.
What do you think about the patch below?
Oleg.
--- 26-rc2/kernel/workqueue.c~WQ_CPU_UP_PREPARE 2008-07-12 19:40:57.000000000 +0400
+++ 26-rc2/kernel/workqueue.c 2008-07-22 13:15:16.000000000 +0400
@@ -911,6 +911,7 @@ static int __devinit workqueue_cpu_callb
unsigned int cpu = (unsigned long)hcpu;
struct cpu_workqueue_struct *cwq;
struct workqueue_struct *wq;
+ int ret = NOTIFY_OK;
action &= ~CPU_TASKS_FROZEN;
@@ -919,6 +920,7 @@ static int __devinit workqueue_cpu_callb
cpu_set(cpu, cpu_populated_map);
}
+cancel:
list_for_each_entry(wq, &workqueues, list) {
cwq = per_cpu_ptr(wq->cpu_wq, cpu);
@@ -928,7 +930,9 @@ static int __devinit workqueue_cpu_callb
break;
printk(KERN_ERR "workqueue [%s] for %i failed\n",
wq->name, cpu);
- return NOTIFY_BAD;
+ action = CPU_UP_CANCELED;
+ ret = NOTIFY_BAD;
+ goto cancel;
case CPU_ONLINE:
start_workqueue_thread(cwq, cpu);
@@ -948,7 +952,7 @@ static int __devinit workqueue_cpu_callb
cpu_clear(cpu, cpu_populated_map);
}
- return NOTIFY_OK;
+ return ret;
}
void __init init_workqueues(void)
next prev parent reply other threads:[~2008-07-22 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200807220826.m6M8Q4I6018588@imap1.linux-foundation.org>
2008-07-22 8:45 ` Oleg Nesterov
2008-07-22 8:59 ` Akinobu Mita
2008-07-22 9:16 ` Oleg Nesterov [this message]
2008-07-22 9:55 ` Akinobu Mita
2008-07-22 10:23 ` Oleg Nesterov
2008-07-22 10:27 ` [PATCH] workqueues: do CPU_UP_CANCELED if CPU_UP_PREPARE fails 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=20080722091636.GA241@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/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®