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
| ||
|
Message-ID: <87r16jm1o7.ffs@tglx> Date: Thu, 31 Mar 2022 02:00:08 +0200 From: Thomas Gleixner <tglx@...utronix.de> To: Song Liu <song@...nel.org>, linux-mm@...ck.org, bpf@...r.kernel.org, netdev@...r.kernel.org, x86@...nel.org Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org, kernel-team@...com, akpm@...ux-foundation.org, pmenzel@...gen.mpg.de, rick.p.edgecombe@...el.com, Song Liu <song@...nel.org> Subject: Re: [PATCH bpf 4/4] bpf: use __vmalloc_node_range() with VM_TRY_HUGE_VMAP for bpf_prog_pack On Wed, Mar 30 2022 at 15:56, Song Liu wrote: > We cannot yet savely enable HAVE_ARCH_HUGE_VMAP for all vmalloc in X86_64. > Let bpf_prog_pack to call __vmalloc_node_range() with VM_TRY_HUGE_VMAP > directly. Again, this changelog lacks any form of reasoning and justification. Aside of that there is absolutely nothing x86_64 specific in the patch. You might know all the details behind this change today, but will you be able to make sense of the above half a year from now? Even if you can, then anyone else is left in the dark. Thanks, tglx
Powered by blists - more mailing lists