Subject mseal sysmap: Choose system mapping sealing at boot
Author chris@chrisdown.name
Date 2026-10-27 11:43:04 +0000 UTC
Version
Cc akpm@linux-foundation.org alexander@mihalicyn.com avagin@gmail.com chris@chrisdown.name corbet@lwn.net david@kernel.org jannh@google.com jeffxu@chromium.org jmorris@namei.org kees@kernel.org kernel-team@meta.com liam@infradead.org linux-doc@vger.kernel.org linux-hardening@vger.kernel.org linux-kernel@vger.kernel.org linux-kselftest@vger.kernel.org linux-mm@kvack.org linux-security-module@vger.kernel.org ljs@kernel.org paul@paul-moore.com pfalcato@suse.de serge@hallyn.com shuah@kernel.org vbabka@kernel.org
Patches (3)
Name Content [All]
[PATCH 1/3] mseal sysmap: Add mseal_system_mappings= boot parameter [Body]
[PATCH 2/3] mseal sysmap: Allow with CHECKPOINT_RESTORE, default off [Body]
[PATCH 3/3] selftests/mseal_system_mappings: Test vdso unmap and remap [Body]
Series Summary
skipped
Session skipped: AI determined the patch has no functional impact
Sessions
Session 2026-10-27
skipped
ID (for dev) efb58a23-c78c-451c-b2a1-5bcd994aaa29
Status skipped
Triaged Skipped: AI determined the patch has no functional impact [Log] [Trajectory]
Execution Log [Link]
Test Base Patched Verdict