[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202401091144.2C203AA7@keescook>
Date: Tue, 9 Jan 2024 11:47:13 -0800
From: Kees Cook <keescook@...omium.org>
To: jeffxu@...omium.org
Cc: akpm@...ux-foundation.org, jannh@...gle.com, sroettger@...gle.com,
willy@...radead.org, gregkh@...uxfoundation.org,
torvalds@...ux-foundation.org, usama.anjum@...labora.com,
jeffxu@...gle.com, jorgelo@...omium.org, groeck@...omium.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-mm@...ck.org, pedro.falcato@...il.com, dave.hansen@...el.com,
linux-hardening@...r.kernel.org, deraadt@...nbsd.org
Subject: Re: [RFC PATCH v5 0/4] Introduce mseal()
On Tue, Jan 09, 2024 at 03:45:38PM +0000, jeffxu@...omium.org wrote:
> This patchset proposes a new mseal() syscall for the Linux kernel.
Thanks for continuing to work on this! Given Linus's general approval
on the v4, I think this series can also drop the "RFC" part -- this code
is looking to land. :)
Since we're in the merge window right now, it'll likely be a couple
weeks before akpm will consider putting this in -next. But given timing,
this means it'll have a long time to bake in -next, which is good.
-Kees
--
Kees Cook
Powered by blists - more mailing lists