From: Namhyung Kim <namhyung@kernel.org>
To: Hillf Danton <dhillf@gmail.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>, Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] stop_machine: check work->done while handling enqueued works
Date: Fri, 08 Feb 2013 17:21:27 +0900 [thread overview]
Message-ID: <87txpnqkqg.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <CAJd=RBD4ZJN7uXQ5xY1GF14j_DydDQEpuZNct-UiNXTBARpQSQ@mail.gmail.com> (Hillf Danton's message of "Fri, 8 Feb 2013 11:39:56 +0800")
Hi Hillf,
On Fri, 8 Feb 2013 11:39:56 +0800, Hillf Danton wrote:
> The comment just above cpu_stop_signal_done() says it is uncertain that
> the input @done is valid, and the works enqueued through the function
> stop_one_cpu_nowait() do carry no done, thus we have to check if it is
> valid when updating work result.
The only user of stop_one_cpu_nowait() is the scheduler active balancer
and active_load_balance_cpu_stop() always returns 0. But I think this
change makes its sense and the code evolves, so:
Reviewed-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
>
> Signed-off-by: Hillf Danton <dhillf@gmail.com>
> ---
>
> --- a/kernel/stop_machine.c Thu Feb 7 20:03:10 2013
> +++ b/kernel/stop_machine.c Fri Feb 8 11:07:40 2013
> @@ -279,7 +279,7 @@ repeat:
> preempt_disable();
>
> ret = fn(arg);
> - if (ret)
> + if (ret && done != NULL)
> done->ret = ret;
>
> /* restore preemption and check it's still balanced */
> --
next prev parent reply other threads:[~2013-02-08 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 3:39 Hillf Danton
2013-02-08 8:21 ` Namhyung Kim [this message]
2013-02-09 19:08 ` Tejun Heo
2013-02-10 4:18 ` Hillf Danton
2013-02-10 5:22 Hillf Danton
2013-02-12 17:37 ` 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=87txpnqkqg.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dhillf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tj@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®