Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 4 Jul 2019 12:53:49 -0700
From: Andrew Morton <>
To: Alexander Potapenko <>
Cc: Christoph Lameter <>, Kees Cook <>,
 Michal Hocko <>, James Morris
 <>, 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 <>, Qian Cai <>, Linux Memory Management
 List <>, linux-security-module
 <>, Kernel Hardening
Subject: Re: [PATCH v10 1/2] mm: security: introduce init_on_alloc=1 and
 init_on_free=1 boot options

On Wed, 3 Jul 2019 13:40:26 +0200 Alexander Potapenko <> wrote:

> > There are unchangelogged alterations between v9 and v10.  The
> > replacement of IS_ENABLED(CONFIG_PAGE_POISONING)) with
> > page_poisoning_enabled().
> In the case I send another version of the patch, do I need to
> retroactively add them to the changelog?

I don't think the world could stand another version ;)

Please simply explain this change for the reviewers?

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.