Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 31 May 2019 18:18:32 -0700
From: Andrew Morton <>
To: Alexander Potapenko <>
Cc: Christoph Lameter <>, Kees Cook <>,
 Dmitry Vyukov <>, James Morris <>, Jann
 Horn <>, Kostya Serebryany <>, Laura Abbott
 <>, Mark Rutland <>, Masahiro Yamada
 <>, Matthew Wilcox <>, Nick
 Desaulniers <>, Randy Dunlap
 <>, Sandeep Patil <>,
 "Serge E. Hallyn" <>, Souptick Joarder
 <>, Marco Elver <>,,,
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 <> wrote:

> Print the currently enabled stack and heap initialization modes.
> The possible options for stack are:
>  - "all" for CONFIG_INIT_STACK_ALL;
>  - "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".


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.


> 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.