From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: jeffxu@chromium.org
Cc: akpm@linux-foundation.org, keescook@chromium.org,
jannh@google.com, torvalds@linux-foundation.org, vbabka@suse.cz,
Liam.Howlett@oracle.com, adhemerval.zanella@linaro.org,
oleg@redhat.com, avagin@gmail.com, benjamin@sipsolutions.net,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
jorgelo@chromium.org, sroettger@google.com, hch@lst.de,
ojeda@kernel.org, thomas.weissschuh@linutronix.de,
adobriyan@gmail.com, johannes@sipsolutions.net,
pedro.falcato@gmail.com, hca@linux.ibm.com, willy@infradead.org,
anna-maria@linutronix.de, mark.rutland@arm.com,
linus.walleij@linaro.org, Jason@zx2c4.com, deller@gmx.de,
rdunlap@infradead.org, davem@davemloft.net, peterx@redhat.com,
f.fainelli@gmail.com, gerg@kernel.org,
dave.hansen@linux.intel.com, mingo@kernel.org, ardb@kernel.org,
mhocko@suse.com, 42.hyeyoo@gmail.com, peterz@infradead.org,
ardb@google.com, enh@google.com, rientjes@google.com,
groeck@chromium.org, mpe@ellerman.id.au,
aleksandr.mikhalitsyn@canonical.com, mike.rapoport@gmail.com,
Kees Cook <kees@kernel.org>
Subject: Re: [PATCH v8 6/7] mseal sysmap: update mseal.rst
Date: Mon, 3 Mar 2025 11:57:10 +0000 [thread overview]
Message-ID: <b7f22fb4-d8dd-48e7-9b12-3a26dc645513@lucifer.local> (raw)
In-Reply-To: <20250303050921.3033083-7-jeffxu@google.com>
On Mon, Mar 03, 2025 at 05:09:20AM +0000, jeffxu@chromium.org wrote:
> From: Jeff Xu <jeffxu@chromium.org>
>
> Update memory sealing documentation to include details about system
> mappings.
>
> Signed-off-by: Jeff Xu <jeffxu@chromium.org>
> Reviewed-by: Kees Cook <kees@kernel.org>
LGTM so:
Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
> Documentation/userspace-api/mseal.rst | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/Documentation/userspace-api/mseal.rst b/Documentation/userspace-api/mseal.rst
> index 41102f74c5e2..76e10938302a 100644
> --- a/Documentation/userspace-api/mseal.rst
> +++ b/Documentation/userspace-api/mseal.rst
> @@ -130,6 +130,26 @@ Use cases
>
> - Chrome browser: protect some security sensitive data structures.
>
> +- System mappings:
> + The system mappings are created by the kernel and includes vdso, vvar,
> + vvar_vclock, vectors (arm compact-mode), sigpage (arm compact-mode), uprobes.
> +
> + Those system mappings are readonly only or execute only, memory sealing can
> + protect them from ever changing to writable or unmmap/remapped as different
> + attributes. This is useful to mitigate memory corruption issues where a
> + corrupted pointer is passed to a memory management system.
> +
> + If supported by an architecture (CONFIG_ARCH_SUPPORTS_MSEAL_SYSTEM_MAPPINGS),
> + the CONFIG_MSEAL_SYSTEM_MAPPINGS seals all system mappings of this
> + architecture.
> +
> + The following architectures currently support this feature: x86-64 and arm64.
> +
> + WARNING: This feature breaks programs which rely on relocating
> + or unmapping system mappings. Known broken software at the time
> + of writing includes CHECKPOINT_RESTORE, UML, gVisor, rr. Therefore
> + this config can't be enabled universally.
Perfect, thanks!
> +
> When not to use mseal
> =====================
> Applications can apply sealing to any virtual memory region from userspace,
> --
> 2.48.1.711.g2feabab25a-goog
>
next prev parent reply other threads:[~2025-03-03 11:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 5:09 [PATCH v8 0/7] mseal system mappings jeffxu
2025-03-03 5:09 ` [PATCH v8 1/7] mseal sysmap: kernel config and header change jeffxu
2025-03-03 11:51 ` Lorenzo Stoakes
2025-03-03 15:02 ` Liam R. Howlett
2025-03-03 16:37 ` Kees Cook
2025-03-03 19:29 ` Jeff Xu
2025-03-03 5:09 ` [PATCH v8 2/7] selftests: x86: test_mremap_vdso: skip if vdso is msealed jeffxu
2025-03-03 15:00 ` Liam R. Howlett
2025-03-03 5:09 ` [PATCH v8 3/7] mseal sysmap: enable x86-64 jeffxu
2025-03-03 11:53 ` Lorenzo Stoakes
2025-03-03 12:01 ` Lorenzo Stoakes
2025-03-03 19:34 ` Jeff Xu
2025-03-03 15:03 ` Liam R. Howlett
2025-03-03 16:38 ` Kees Cook
2025-03-03 5:09 ` [PATCH v8 4/7] mseal sysmap: enable arm64 jeffxu
2025-03-03 11:53 ` Lorenzo Stoakes
2025-03-03 15:04 ` Liam R. Howlett
2025-03-03 16:39 ` Kees Cook
2025-03-03 5:09 ` [PATCH v8 5/7] mseal sysmap: uprobe mapping jeffxu
2025-03-03 6:28 ` Oleg Nesterov
2025-03-03 11:54 ` Lorenzo Stoakes
2025-03-03 15:04 ` Liam R. Howlett
2025-03-03 16:39 ` Kees Cook
2025-03-03 5:09 ` [PATCH v8 6/7] mseal sysmap: update mseal.rst jeffxu
2025-03-03 11:57 ` Lorenzo Stoakes [this message]
2025-03-03 15:05 ` Liam R. Howlett
2025-03-03 5:09 ` [PATCH v8 7/7] selftest: test system mappings are sealed jeffxu
2025-03-03 12:08 ` Lorenzo Stoakes
2025-03-03 16:43 ` Lorenzo Stoakes
2025-03-03 16:48 ` Kees Cook
2025-03-03 19:46 ` Jeff Xu
2025-03-03 16:47 ` Kees Cook
2025-03-03 16:49 ` Lorenzo Stoakes
2025-03-03 17:01 ` Kees Cook
2025-03-03 20:20 ` Jeff Xu
2025-03-04 20:53 ` Jeff Xu
2025-03-03 11:50 ` [PATCH v8 0/7] mseal system mappings Lorenzo Stoakes
2025-03-03 14:59 ` Liam R. Howlett
2025-03-03 16:33 ` Kees Cook
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=b7f22fb4-d8dd-48e7-9b12-3a26dc645513@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=42.hyeyoo@gmail.com \
--cc=Jason@zx2c4.com \
--cc=Liam.Howlett@oracle.com \
--cc=adhemerval.zanella@linaro.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=anna-maria@linutronix.de \
--cc=ardb@google.com \
--cc=ardb@kernel.org \
--cc=avagin@gmail.com \
--cc=benjamin@sipsolutions.net \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=enh@google.com \
--cc=f.fainelli@gmail.com \
--cc=gerg@kernel.org \
--cc=groeck@chromium.org \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=jannh@google.com \
--cc=jeffxu@chromium.org \
--cc=johannes@sipsolutions.net \
--cc=jorgelo@chromium.org \
--cc=kees@kernel.org \
--cc=keescook@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=mike.rapoport@gmail.com \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=ojeda@kernel.org \
--cc=oleg@redhat.com \
--cc=pedro.falcato@gmail.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=sroettger@google.com \
--cc=thomas.weissschuh@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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