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
| ||
|
Date: Fri, 16 Dec 2022 12:35:10 -0800 From: Kees Cook <keescook@...omium.org> To: Jeff Xu <jeffxu@...gle.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, Peter Xu <peterx@...hat.com>, jeffxu@...omium.org, skhan@...uxfoundation.org, dmitry.torokhov@...il.com, dverkamp@...omium.org, hughd@...gle.com, jorgelo@...omium.org, linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org, linux-mm@...ck.org, jannh@...gle.com, linux-hardening@...r.kernel.org, kernel test robot <lkp@...el.com> Subject: Re: [PATCH v6 3/6] mm/memfd: add MFD_NOEXEC_SEAL and MFD_EXEC On Fri, Dec 16, 2022 at 10:11:44AM -0800, Jeff Xu wrote: > Once per boot seems too little, it would be nice if we can list all processes. > I agree ratelimited might be too much. > There is a feature gap here for logging. > > Kees, what do you think ? I agree once per boot is kind of frustrating "I fixed the one warning, oh, now it's coming from a different process". But ratelimit is, in retrospect, still too often. Let's go with per boot -- this should be noisy "enough" to get the changes in API into the callers without being too much of a hassle. -- Kees Cook
Powered by blists - more mailing lists