Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 17 Jun 2019 22:26:54 -0700
From: Kees Cook <>
To: Andrew Morton <>
Cc: Alexander Potapenko <>,
	Christoph Lameter <>,
	Masahiro Yamada <>,
	Michal Hocko <>, James Morris <>,
	"Serge E. Hallyn" <>,
	Nick Desaulniers <>,
	Kostya Serebryany <>,
	Dmitry Vyukov <>,
	Sandeep Patil <>,
	Laura Abbott <>,
	Randy Dunlap <>, Jann Horn <>,
	Mark Rutland <>, Marco Elver <>,,,
Subject: Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and
 init_on_free=1 boot options

On Mon, Jun 17, 2019 at 10:19:32PM -0700, Andrew Morton wrote:
> On Mon, 17 Jun 2019 22:07:41 -0700 Kees Cook <> wrote:
> > This is expected to be on-by-default on Android and Chrome
> > OS. And it gives the opportunity for anyone else to use it under distros
> > too via the boot args. (The init_on_free feature is regularly requested
> > by folks where memory forensics is included in their thread models.)
> Thanks.  I added the above to the changelog.  I assumed s/thread/threat/

Heh whoops, yes, "threat" was intended. Thanks! :)

Kees Cook

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.