[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74b8e4c0-a557-b047-4507-c243c9aad216@gmail.com>
Date: Fri, 2 Jun 2023 09:15:25 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Kees Cook <keescook@...omium.org>, Vlastimil Babka <vbabka@...e.cz>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>,
Linux Memory Management List <linux-mm@...ck.org>,
Jeff Xu <jeffxu@...gle.com>,
Daniel Verkamp <dverkamp@...omium.org>,
David Herrmann <dh.herrmann@...il.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Hugh Dickins <hughd@...gle.com>, Jann Horn <jannh@...gle.com>,
Jorge Lucangeli Obes <jorgelo@...omium.org>,
Shuah Khan <skhan@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Stuart Foster <smf-linux@...ginmedia.com>
Subject: Re: Fwd: Started to get "memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL"
On 6/1/23 21:12, Kees Cook wrote:
>> Hm indeed it seems to have introduced 2 new flags and immediately warn if
>> any process doesn't use them. Maybe it would make sense for some of the
>> non-default values of vm.memfd_noexec, but it's too early to warn
>> unconditionally everywhere, no?
>
> This is pretty standard for getting new options like this noticed by
> userspace -- there is no regression in _behavior_. It's just a reminder
> to fix userspace code.
>
Telling regzbot:
#regzbot invalid: not a kernel regression, but userspace fix is needed
Thanks.
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists