[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <871q646rea.fsf@meer.lwn.net>
Date: Tue, 14 May 2024 14:59:57 -0600
From: Jonathan Corbet <corbet@....net>
To: Andrew Morton <akpm@...ux-foundation.org>, jeffxu@...omium.org
Cc: keescook@...omium.org, jannh@...gle.com, sroettger@...gle.com,
willy@...radead.org, gregkh@...uxfoundation.org,
torvalds@...ux-foundation.org, usama.anjum@...labora.com,
Liam.Howlett@...cle.com, surenb@...gle.com, merimus@...gle.com,
rdunlap@...radead.org, 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: [PATCH v10 0/5] Introduce mseal
Andrew Morton <akpm@...ux-foundation.org> writes:
> On Mon, 15 Apr 2024 16:35:19 +0000 jeffxu@...omium.org wrote:
>
>> This patchset proposes a new mseal() syscall for the Linux kernel.
>
> I have not moved this into mm-stable for a 6.10 merge. Mainly because
> of the total lack of Reviewed-by:s and Acked-by:s.
>
> The code appears to be stable enough for a merge.
>
> It's awkward that we're in conference this week, but I ask people to
> give consideration to the desirability of moving mseal() into mainline
> sometime over the next week, please.
I hate to be obnoxious, but I *was* copied ... :)
Not taking a position on merging, but I have to ask: are we convinced at
this point that mseal() isn't a chrome-only system call? Did we ever
see the glibc patches that were promised?
Thanks,
jon
Powered by blists - more mailing lists