Date: Tue, 16 Apr 2019 10:30:20 +0200 From: Vlastimil Babka <vbabka@...e.cz> To: Alexander Potapenko <glider@...gle.com>, akpm@...ux-foundation.org Cc: linux-security-module@...r.kernel.org, linux-mm@...ck.org, ndesaulniers@...gle.com, kcc@...gle.com, dvyukov@...gle.com, keescook@...omium.org, sspatil@...roid.com, labbott@...hat.com, kernel-hardening@...ts.openwall.com Subject: Re: [PATCH] mm: security: introduce CONFIG_INIT_HEAP_ALL On 4/12/19 2:45 PM, Alexander Potapenko wrote: > +config INIT_HEAP_ALL > + bool "Initialize kernel heap allocations" Calling slab and page allocations together as "heap" is rather uncommon in the kernel I think. But I don't have a better word right now. > + default n > + help > + Enforce initialization of pages allocated from page allocator > + and objects returned by kmalloc and friends. > + Allocated memory is initialized with zeroes, preventing possible > + information leaks and making the control-flow bugs that depend > + on uninitialized values more deterministic. > + > config GCC_PLUGIN_STRUCTLEAK_VERBOSE > bool "Report forcefully initialized variables" > depends on GCC_PLUGIN_STRUCTLEAK >
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.