[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 4 Jul 2019 12:53:49 -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>,
Michal Hocko <mhocko@...e.com>, James Morris
<jamorris@...ux.microsoft.com>, Masahiro Yamada
<yamada.masahiro@...ionext.com>, Michal Hocko <mhocko@...nel.org>, James
Morris <jmorris@...ei.org>, "Serge E. Hallyn" <serge@...lyn.com>, Nick
Desaulniers <ndesaulniers@...gle.com>, Kostya Serebryany <kcc@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>, Sandeep Patil <sspatil@...roid.com>,
Laura Abbott <labbott@...hat.com>, Randy Dunlap <rdunlap@...radead.org>,
Jann Horn <jannh@...gle.com>, Mark Rutland <mark.rutland@....com>, Marco
Elver <elver@...gle.com>, Qian Cai <cai@....pw>, Linux Memory Management
List <linux-mm@...ck.org>, linux-security-module
<linux-security-module@...r.kernel.org>, Kernel Hardening
<kernel-hardening@...ts.openwall.com>
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 <glider@...gle.com> 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.
