[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023121343-scalping-urging-0dbc@gregkh>
Date: Wed, 13 Dec 2023 08:24:39 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: jeffxu@...omium.org
Cc: akpm@...ux-foundation.org, keescook@...omium.org, jannh@...gle.com,
sroettger@...gle.com, willy@...radead.org,
torvalds@...ux-foundation.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: [RFC PATCH v3 01/11] mseal: Add mseal syscall.
On Tue, Dec 12, 2023 at 11:16:55PM +0000, jeffxu@...omium.org wrote:
> +config MSEAL
> + default n
Minor nit, "n" is always the default, no need to call it out here.
> + bool "Enable mseal() system call"
> + depends on MMU
> + help
> + Enable the virtual memory sealing.
> + This feature allows sealing each virtual memory area separately with
> + multiple sealing types.
You might want to include more documentation as to what this is for,
otherwise distros / users will not know if they need to enable this
or not.
thanks,
greg k-h
Powered by blists - more mailing lists