From: Greg KH <gregkh@linuxfoundation.org>
To: guoren@kernel.org
Cc: arnd@arndb.de, palmer@dabbelt.com, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Guo Ren <guoren@linux.alibaba.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH V3] riscv: patch_text: Fixup last cpu should be master
Date: Wed, 6 Apr 2022 20:13:36 +0200 [thread overview]
Message-ID: <Yk3YUFfvEszb+cXT@kroah.com> (raw)
In-Reply-To: <20220406141649.728971-1-guoren@kernel.org>
On Wed, Apr 06, 2022 at 10:16:49PM +0800, guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> These patch_text implementations are using stop_machine_cpuslocked
> infrastructure with atomic cpu_count. The original idea: When the
> master CPU patch_text, the others should wait for it. But current
> implementation is using the first CPU as master, which couldn't
> guarantee the remaining CPUs are waiting. This patch changes the
> last CPU as the master to solve the potential risk.
>
> Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
> Signed-off-by: Guo Ren <guoren@kernel.org>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
> Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org>
> Cc: <stable@vger.kernel.org>
> ---
> arch/riscv/kernel/patch.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
What commit id does this change fix?
next prev parent reply other threads:[~2022-04-06 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 14:16 [PATCH V3] riscv: patch_text: Fixup last cpu should be master guoren
2022-04-06 18:13 ` Greg KH [this message]
2022-04-06 19:06 ` Palmer Dabbelt
2022-04-07 6:36 ` Guo Ren
2022-04-07 6:33 ` Guo Ren
2022-04-21 22:57 ` Palmer Dabbelt
2022-04-22 16:02 ` Palmer Dabbelt
2022-04-24 7:33 ` Guo Ren
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=Yk3YUFfvEszb+cXT@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mhiramat@kernel.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=stable@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