From: Heiko Carstens <hca@linux.ibm.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [PATCH v2 00/10] s390: Consistent usage of text_mutex
Date: Tue, 27 Oct 2026 15:30:20 +0100 [thread overview]
Message-ID: <20261027143030.3154657-1-hca@linux.ibm.com> (raw)
v2:
- Use text mutex for all callers of s390_kernel_write(), and add lockdep
checking. [Based on a review comment from Ilya Leoshkevich, and also
Sashiko feedback]
- Note: this takes now the mutex also at places where it is technically
not necessary (e.g. ftrace init nop patching). However this is not much
of a difference to before, where the spinlock in s390_kernel_write()
was always taken instead
v1:
Other architectures serialize kernel text patching with text_mutex. s390
does not: __s390_kernel_write() relies on a private spinlock, and callers
partially depend on implicit exclusion (e.g. no kprobe can be set on a
jump label).
Make s390 consistent with other architectures:
- Patches 1-3 add text_mutex to the jump_label, ftrace and bpf text
patching paths
- Patch 4 removes the redundant spinlock from __s390_kernel_write().
CPU serialization, previously done implicitly, is now explicit via
sync_core()
Thanks,
Heiko
Heiko Carstens (10):
s390/jump_label: Serialize text patching with text_mutex
s390/ftrace: Serialize text patching with text_mutex
s390/bpf: Serialize text patching with text_mutex
s390/runtime-const: Serialize text patching with text_mutex
s390/module: Serialize text patching with text_mutex
s390/stackprotector: Serialize text patching with text_mutex
s390/nospec-branch: Serialize text patching with text_mutex
s390/alternative: Serialize text patching with text_mutex
s390/uaccess: Move s390_kernel_write() to asm/text-patching.h
s390/maccess: Remove spinlock from __s390_kernel_write()
arch/s390/include/asm/runtime-const.h | 4 +++-
arch/s390/include/asm/text-patching.h | 14 ++++++++++++++
arch/s390/include/asm/uaccess.h | 9 ---------
arch/s390/kernel/alternative.c | 6 +++++-
arch/s390/kernel/ftrace.c | 11 +++++++++++
arch/s390/kernel/jump_label.c | 3 ++-
arch/s390/kernel/kprobes.c | 4 +++-
arch/s390/kernel/module.c | 2 ++
arch/s390/kernel/nospec-branch.c | 4 ++++
arch/s390/kernel/stackprotector.c | 6 +++++-
arch/s390/mm/maccess.c | 9 ++++-----
arch/s390/net/bpf_jit_comp.c | 21 +++++++++++++++++----
12 files changed, 70 insertions(+), 23 deletions(-)
--
2.53.0
next reply other threads:[~2026-10-27 14:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 14:30 Heiko Carstens [this message]
2026-10-27 14:30 ` [PATCH v2 01/10] s390/jump_label: Serialize text patching with text_mutex Heiko Carstens
2026-10-28 10:50 ` Ilya Leoshkevich
2026-10-27 14:30 ` [PATCH v2 02/10] s390/ftrace: " Heiko Carstens
2026-10-28 10:54 ` Ilya Leoshkevich
2026-10-27 14:30 ` [PATCH v2 03/10] s390/bpf: " Heiko Carstens
2026-10-28 10:56 ` Ilya Leoshkevich
2026-10-27 14:30 ` [PATCH v2 04/10] s390/runtime-const: " Heiko Carstens
2026-10-28 10:58 ` Ilya Leoshkevich
2026-10-28 11:09 ` Heiko Carstens
2026-10-28 12:22 ` Ilya Leoshkevich
2026-10-28 13:43 ` Heiko Carstens
2026-10-27 14:30 ` [PATCH v2 05/10] s390/module: " Heiko Carstens
2026-10-28 10:59 ` Ilya Leoshkevich
2026-10-27 14:30 ` [PATCH v2 06/10] s390/stackprotector: " Heiko Carstens
2026-10-28 12:23 ` Ilya Leoshkevich
2026-10-27 14:30 ` [PATCH v2 07/10] s390/nospec-branch: " Heiko Carstens
2026-10-28 12:24 ` Ilya Leoshkevich
2026-10-27 14:30 ` [PATCH v2 08/10] s390/alternative: " Heiko Carstens
2026-10-28 12:25 ` Ilya Leoshkevich
2026-10-27 14:30 ` [PATCH v2 09/10] s390/uaccess: Move s390_kernel_write() to asm/text-patching.h Heiko Carstens
2026-10-28 12:26 ` Ilya Leoshkevich
2026-10-27 14:30 ` [PATCH v2 10/10] s390/maccess: Remove spinlock from __s390_kernel_write() Heiko Carstens
2026-10-28 20:59 ` Ilya Leoshkevich
2026-10-29 10:57 ` Heiko Carstens
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=20261027143030.3154657-1-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.com \
/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®