From: guoren@kernel.org
To: guoren@kernel.org, arnd@arndb.de, gregkh@linuxfoundation.org
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-csky@vger.kernel.org, linux-xtensa@linux-xtensa.org,
linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Guo Ren <guoren@linux.alibaba.com>
Subject: [PATCH V4 0/4] arch: patch_text: Fixup last cpu should be master
Date: Thu, 7 Apr 2022 15:33:19 +0800 [thread overview]
Message-ID: <20220407073323.743224-1-guoren@kernel.org> (raw)
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.
Changes in v4:
- Add "Fixes:" for stable fixup
- Add cover letter for the patch series
Changes in v3:
- Separate the patch for different arch.
Changes in v2:
- Fixup num_online_cpus() - 1 is not last cpu
Guo Ren (4):
arm64: patch_text: Fixup last cpu should be master
riscv: patch_text: Fixup last cpu should be master
xtensa: patch_text: Fixup last cpu should be master
csky: patch_text: Fixup last cpu should be master
arch/arm64/kernel/patching.c | 4 ++--
arch/csky/kernel/probes/kprobes.c | 2 +-
arch/riscv/kernel/patch.c | 2 +-
arch/xtensa/kernel/jump_label.c | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2022-04-07 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 7:33 guoren [this message]
2022-04-07 7:33 ` [PATCH V4 1/4] arm64: patch_text: Fixup last cpu should be master guoren
2022-04-07 7:33 ` [PATCH V4 2/4] riscv: " guoren
2022-04-07 7:33 ` [PATCH V4 3/4] xtensa: " guoren
2022-04-07 7:33 ` [PATCH V4 4/4] csky: " guoren
2022-04-08 13:58 ` [PATCH V4 0/4] arch: " Will Deacon
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=20220407073323.743224-1-guoren@kernel.org \
--to=guoren@kernel.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=guoren@linux.alibaba.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-xtensa@linux-xtensa.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;
as well as URLs for NNTP newsgroup(s).