Re: [PATCH v8 0/7] mseal system mappings

2025-03-03 Thread Kees Cook
On Mon, Mar 03, 2025 at 09:59:13AM -0500, Liam R. Howlett wrote: > * jef...@chromium.org [250303 00:09]: > > ... > > > > > Link: > > https://lore.kernel.org/all/20240415163527.626541-1-jef...@chromium.org/ [1] > > Link: Documentation/userspace-api/mseal.rst [2] > > Link: > > https://lore.kern

Re: [PATCH v8 0/7] mseal system mappings

2025-03-03 Thread Liam R. Howlett
* jef...@chromium.org [250303 00:09]: ... > > Link: > https://lore.kernel.org/all/20240415163527.626541-1-jef...@chromium.org/ [1] > Link: Documentation/userspace-api/mseal.rst [2] > Link: > https://lore.kernel.org/all/cabi2sku9brunqf70-nksumcq+yyiwjo3fm4xkrkl-nrczxy...@mail.gmail.com/ > [3]

Re: [PATCH v8 0/7] mseal system mappings

2025-03-03 Thread Lorenzo Stoakes
Great nice descriptions thanks! On Mon, Mar 03, 2025 at 05:09:14AM +, jef...@chromium.org wrote: > From: Jeff Xu > > This is V8 version, addressing comments from V7, without code logic > change. > > --- > As discussed during msea

[PATCH v8 0/7] mseal system mappings

2025-03-02 Thread jeffxu
From: Jeff Xu This is V8 version, addressing comments from V7, without code logic change. --- As discussed during mseal() upstream process [1], mseal() protects the VMAs of a given virtual memory range against modifications, such as