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 0/2] mseal system mappings fix + s390 enablement
Date: Tue, 11 Mar 2025 13:33:24 +0100 [thread overview]
Message-ID: <20250311123326.2686682-1-hca@linux.ibm.com> (raw)
When rebasing the mseal series on top of the generic vdso data storage
the VM_SEALED_SYSMAP vm flag for the vvar mapping got lost. Add that again.
Also add s390 support for MSEAL_SYSTEM_MAPPINGS.
Heiko Carstens (2):
mseal sysmap: generic vdso vvar mapping
mseal sysmap: enable s390
arch/s390/Kconfig | 1 +
arch/s390/kernel/vdso.c | 2 +-
lib/vdso/datastore.c | 3 ++-
3 files changed, 4 insertions(+), 2 deletions(-)
--
2.45.2
next reply other threads:[~2025-03-11 12:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 12:33 Heiko Carstens [this message]
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 ` [PATCH mm-unstable 2/2] mseal sysmap: enable s390 Heiko Carstens
2025-03-11 14:37 ` 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-1-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 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.