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 0/4] s390: Consistent usage of text_mutex
Date: Mon, 26 Oct 2026 13:03:25 +0100 [thread overview]
Message-ID: <20261026120329.1792436-1-hca@linux.ibm.com> (raw)
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 (4):
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/maccess: Remove spinlock from __s390_kernel_write()
arch/s390/kernel/ftrace.c | 9 +++++++++
arch/s390/kernel/jump_label.c | 3 +++
arch/s390/mm/maccess.c | 9 ++++-----
arch/s390/net/bpf_jit_comp.c | 21 +++++++++++++++++----
4 files changed, 33 insertions(+), 9 deletions(-)
--
2.53.0
next reply other threads:[~2026-10-26 12:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 12:03 Heiko Carstens [this message]
2026-10-26 12:03 ` [PATCH 1/4] s390/jump_label: Serialize text patching with text_mutex Heiko Carstens
2026-10-26 12:16 ` sashiko-bot
2026-10-26 12:03 ` [PATCH 2/4] s390/ftrace: " Heiko Carstens
2026-10-26 12:24 ` sashiko-bot
2026-10-26 12:03 ` [PATCH 3/4] s390/bpf: " Heiko Carstens
2026-10-26 12:28 ` sashiko-bot
2026-10-26 12:03 ` [PATCH 4/4] s390/maccess: Remove spinlock from __s390_kernel_write() Heiko Carstens
2026-10-26 12:40 ` sashiko-bot
2026-10-26 13:04 ` Ilya Leoshkevich
2026-10-26 14:19 ` Heiko Carstens
2026-10-27 10:09 ` kernel test robot
2026-10-27 10:09 ` kernel test robot
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=20261026120329.1792436-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.