[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250311123326.2686682-1-hca@linux.ibm.com>
Date: Tue, 11 Mar 2025 13:33:24 +0100
From: Heiko Carstens <hca@...ux.ibm.com>
To: Andrew Morton <akpm@...ux-foundation.org>, Jeff Xu <jeffxu@...omium.org>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
"Liam R . Howlett" <Liam.Howlett@...cle.com>,
Kees Cook <kees@...nel.org>,
Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: Alexander Gordeev <agordeev@...ux.ibm.com>,
Sven Schnelle <svens@...ux.ibm.com>, Vasily Gorbik <gor@...ux.ibm.com>,
Christian Borntraeger <borntraeger@...ux.ibm.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-hardening@...r.kernel.org
Subject: [PATCH mm-unstable 0/2] mseal system mappings fix + s390 enablement
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
Powered by blists - more mailing lists