Received-SPF: pass (google.com: domain of linux-kernel+bounces-21716-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Precedence: bulk
MIME-Version: 1.0
References: <20240109154547.1839886-1-jeffxu@chromium.org> <202401091144.2C203AA7@keescook>
In-Reply-To: <202401091144.2C203AA7@keescook>
From: Jeff Xu <jeffxu@chromium.org>
Date: Tue, 9 Jan 2024 21:10:01 -0800
Message-ID: <CABi2SkVGW5n0NJqa_1RHnXt=GEizm0ixvGiu+F_mStFwx7pjQw@mail.gmail.com>
Subject: Re: [RFC PATCH v5 0/4] Introduce mseal()
To: Kees Cook <keescook@chromium.org>
Cc: akpm@linux-foundation.org, jannh@google.com, sroettger@google.com, 
	willy@infradead.org, gregkh@linuxfoundation.org, 
	torvalds@linux-foundation.org, usama.anjum@collabora.com, jeffxu@google.com, 
	jorgelo@chromium.org, groeck@chromium.org, linux-kernel@vger.kernel.org, 
	linux-kselftest@vger.kernel.org, linux-mm@kvack.org, pedro.falcato@gmail.com, 
	dave.hansen@intel.com, linux-hardening@vger.kernel.org, deraadt@openbsd.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 9, 2024 at 11:47=E2=80=AFAM Kees Cook <keescook@chromium.org> w=
rote:
>
> On Tue, Jan 09, 2024 at 03:45:38PM +0000, jeffxu@chromium.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. :)
>
OK.

> 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.
>
Thanks for the heads up.
-Jeff

> -Kees

>
> --
> Kees Cook