From: Heiko Carstens <hca@linux.ibm.com>
To: "Andrew Morton" <akpm@linux-foundation.org>,
"Jeff Xu" <jeffxu@chromium.org>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
"Kees Cook" <kees@kernel.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-hardening@vger.kernel.org
Subject: [PATCH mm-unstable 2/2] mseal sysmap: enable s390
Date: Tue, 11 Mar 2025 13:33:26 +0100 [thread overview]
Message-ID: <20250311123326.2686682-3-hca@linux.ibm.com> (raw)
In-Reply-To: <20250311123326.2686682-1-hca@linux.ibm.com>
Provide support for CONFIG_MSEAL_SYSTEM_MAPPINGS on s390, covering the
vdso.
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
---
arch/s390/Kconfig | 1 +
arch/s390/kernel/vdso.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index 608a965e2344..93b880992596 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
@@ -141,6 +141,7 @@ config S390
select ARCH_SUPPORTS_DEBUG_PAGEALLOC
select ARCH_SUPPORTS_HUGETLBFS
select ARCH_SUPPORTS_INT128 if CC_HAS_INT128 && CC_IS_CLANG
+ select ARCH_SUPPORTS_MSEAL_SYSTEM_MAPPINGS
select ARCH_SUPPORTS_NUMA_BALANCING
select ARCH_SUPPORTS_PER_VMA_LOCK
select ARCH_USE_BUILTIN_BSWAP
diff --git a/arch/s390/kernel/vdso.c b/arch/s390/kernel/vdso.c
index 70c8f9ad13cd..430feb1a5013 100644
--- a/arch/s390/kernel/vdso.c
+++ b/arch/s390/kernel/vdso.c
@@ -80,7 +80,7 @@ static int map_vdso(unsigned long addr, unsigned long vdso_mapping_len)
vdso_text_start = vvar_start + VDSO_NR_PAGES * PAGE_SIZE;
/* VM_MAYWRITE for COW so gdb can set breakpoints */
vma = _install_special_mapping(mm, vdso_text_start, vdso_text_len,
- VM_READ|VM_EXEC|
+ VM_READ|VM_EXEC|VM_SEALED_SYSMAP|
VM_MAYREAD|VM_MAYWRITE|VM_MAYEXEC,
vdso_mapping);
if (IS_ERR(vma)) {
--
2.45.2
next prev parent reply other threads:[~2025-03-11 12:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 12:33 [PATCH mm-unstable 0/2] mseal system mappings fix + s390 enablement Heiko Carstens
2025-03-11 12:33 ` [PATCH mm-unstable 1/2] mseal sysmap: generic vdso vvar mapping Heiko Carstens
2025-03-11 12:59 ` Thomas Weißschuh
2025-03-11 13:32 ` Heiko Carstens
2025-03-11 14:36 ` Lorenzo Stoakes
2025-03-11 21:54 ` Jeff Xu
2025-03-11 12:33 ` Heiko Carstens [this message]
2025-03-11 14:37 ` [PATCH mm-unstable 2/2] mseal sysmap: enable s390 Lorenzo Stoakes
2025-03-11 21:55 ` Jeff Xu
2025-03-11 22:12 ` Jeff Xu
2025-03-12 15:39 ` Heiko Carstens
2025-03-12 23:53 ` Jeff Xu
2025-03-11 13:02 ` [PATCH mm-unstable 0/2] mseal system mappings fix + s390 enablement Lorenzo Stoakes
2025-03-11 13:37 ` Heiko Carstens
2025-03-11 13:42 ` Lorenzo Stoakes
2025-03-11 14:06 ` Heiko Carstens
2025-03-11 14:09 ` Lorenzo Stoakes
2025-03-11 14:21 ` Heiko Carstens
2025-03-11 14:30 ` Lorenzo Stoakes
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=20250311123326.2686682-3-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=Liam.Howlett@oracle.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=jeffxu@chromium.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=svens@linux.ibm.com \
--cc=thomas.weissschuh@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