From: Mark Rutland <mark.rutland@arm.com>
To: Rong Tao <rtoax@foxmail.com>
Cc: elver@google.com, linux-kernel@vger.kernel.org,
peterz@infradead.org, rongtao@cestc.cn, tglx@linutronix.de
Subject: Re: [PATCH v2] stop_machine: Avoid potential non-atomic read of multi_stop_data::state
Date: Fri, 20 Oct 2023 11:23:37 +0100 [thread overview]
Message-ID: <ZTJVKbJWqyx2e8Su@FVFF77S0Q05N> (raw)
In-Reply-To: <tencent_4CD220721A6C0B39670D5D52AAE4BD2A8F0A@qq.com>
On Thu, Oct 19, 2023 at 08:11:23AM +0800, Rong Tao wrote:
> From: Rong Tao <rongtao@cestc.cn>
>
> In commit b1fc58333575 ("stop_machine: Avoid potential race behaviour")
> fix both multi_cpu_stop() and set_state() access multi_stop_data::state,
> Pass curstate as a parameter to ack_state(), to avoid the non-atomic read.
Can we please describe this better? This is *not* a fix, it is a cleanup.
As I covered in:
https://lore.kernel.org/lkml/ZS5g6I-UtUnihToH@FVFF77S0Q05N/
... there are no concurrent writers, and so the value of multi_stop_data::state
cannot change, and a non-atomic read is fine.
The actual change looks good to me as it makes it easier to see that there's no
race.
> And replace smp_wmb()+WRITE_ONCE() with smp_store_release().
This is also fine, but feels like a logically separate change.
Mark.
>
> Signed-off-by: Rong Tao <rongtao@cestc.cn>
> ---
> v1: stop_machine: Avoid potential race behaviour of multi_stop_data::state
> https://lore.kernel.org/lkml/tencent_705C16DF25978ACAEBD1E83E228881901006@qq.com/
> ---
> kernel/stop_machine.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/kernel/stop_machine.c b/kernel/stop_machine.c
> index cedb17ba158a..35a122ce2cbd 100644
> --- a/kernel/stop_machine.c
> +++ b/kernel/stop_machine.c
> @@ -183,15 +183,15 @@ static void set_state(struct multi_stop_data *msdata,
> {
> /* Reset ack counter. */
> atomic_set(&msdata->thread_ack, msdata->num_threads);
> - smp_wmb();
> - WRITE_ONCE(msdata->state, newstate);
> + smp_store_release(&msdata->state, newstate);
> }
>
> /* Last one to ack a state moves to the next state. */
> -static void ack_state(struct multi_stop_data *msdata)
> +static void ack_state(struct multi_stop_data *msdata,
> + enum multi_stop_state curstate)
> {
> if (atomic_dec_and_test(&msdata->thread_ack))
> - set_state(msdata, msdata->state + 1);
> + set_state(msdata, curstate + 1);
> }
>
> notrace void __weak stop_machine_yield(const struct cpumask *cpumask)
> @@ -242,7 +242,7 @@ static int multi_cpu_stop(void *data)
> default:
> break;
> }
> - ack_state(msdata);
> + ack_state(msdata, curstate);
> } else if (curstate > MULTI_STOP_PREPARE) {
> /*
> * At this stage all other CPUs we depend on must spin
> --
> 2.42.0
>
next prev parent reply other threads:[~2023-10-20 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 0:11 Rong Tao
2023-10-20 10:23 ` Mark Rutland [this message]
2023-10-20 10:48 ` Peter Zijlstra
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=ZTJVKbJWqyx2e8Su@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.com \
--cc=tglx@linutronix.de \
/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®