linux-kernel - Re: [PATCH v10 0/5] Introduce mseal

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 23 May 2024 16:54:18 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Kees Cook <keescook@...omium.org>
Cc: jeffxu@...omium.org, jannh@...gle.com, sroettger@...gle.com,
 willy@...radead.org, gregkh@...uxfoundation.org,
 torvalds@...ux-foundation.org, usama.anjum@...labora.com, corbet@....net,
 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

On Thu, 23 May 2024 16:32:26 -0700 Kees Cook <keescook@...omium.org> wrote:

> On Tue, May 14, 2024 at 12:52:13PM -0700, Kees Cook wrote:
> > On Tue, May 14, 2024 at 10:46:46AM -0700, Andrew Morton wrote:
> > > 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.
> > 
> > Oh, I thought I had already reviewed it. FWIW, please consider it:
> > 
> > Reviewed-by: Kees Cook <keescook@...omium.org>
> > 
> > > The code appears to be stable enough for a merge.
> > 
> > Agreed.
> > 
> > > 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.
> > 
> > Yes please. :)
> 
> Is the plan still to land this for 6.10? With the testing it's had in
> -next and Liam's review, I think we're good to go?

The testing and implementation review seem OK.  But from a higher-level
perspective Linus doesn't seem to be on board(?).  I was planning on
holding onto this, see if the discussion progresses across this -rc
cycle.