|
Message-Id: <20190531181832.e7c3888870ce9e50db9f69e6@linux-foundation.org> Date: Fri, 31 May 2019 18:18:32 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Alexander Potapenko <glider@...gle.com> Cc: Christoph Lameter <cl@...ux.com>, Kees Cook <keescook@...omium.org>, Dmitry Vyukov <dvyukov@...gle.com>, James Morris <jmorris@...ei.org>, Jann Horn <jannh@...gle.com>, Kostya Serebryany <kcc@...gle.com>, Laura Abbott <labbott@...hat.com>, Mark Rutland <mark.rutland@....com>, Masahiro Yamada <yamada.masahiro@...ionext.com>, Matthew Wilcox <willy@...radead.org>, Nick Desaulniers <ndesaulniers@...gle.com>, Randy Dunlap <rdunlap@...radead.org>, Sandeep Patil <sspatil@...roid.com>, "Serge E. Hallyn" <serge@...lyn.com>, Souptick Joarder <jrdr.linux@...il.com>, Marco Elver <elver@...gle.com>, kernel-hardening@...ts.openwall.com, linux-mm@...ck.org, linux-security-module@...r.kernel.org Subject: Re: [PATCH v5 2/3] mm: init: report memory auto-initialization features at boot time On Wed, 29 May 2019 14:38:11 +0200 Alexander Potapenko <glider@...gle.com> wrote: > Print the currently enabled stack and heap initialization modes. > > The possible options for stack are: > - "all" for CONFIG_INIT_STACK_ALL; > - "byref_all" for CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL; > - "byref" for CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF; > - "__user" for CONFIG_GCC_PLUGIN_STRUCTLEAK_USER; > - "off" otherwise. > > Depending on the values of init_on_alloc and init_on_free boottime > options we also report "heap alloc" and "heap free" as "on"/"off". Why? Please fully describe the benefit to users so that others can judge the desirability of the patch. And so they can review it effectively, etc. Always! > In the init_on_free mode initializing pages at boot time may take some > time, so print a notice about that as well. How much time?
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.