Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 26 Jun 2019 16:28:35 -0700
From: Andrew Morton <>
To: Alexander Potapenko <>
Cc: Christoph Lameter <>, Kees Cook <>,
 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
Subject: Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and
 init_on_free=1 boot options

On Wed, 26 Jun 2019 14:19:42 +0200 Alexander Potapenko <> wrote:

>  v8:
>   - addressed comments by Michal Hocko: revert kernel/kexec_core.c and
>     apply initialization in dma_pool_free()
>   - disable init_on_alloc/init_on_free if slab poisoning or page
>     poisoning are enabled, as requested by Qian Cai
>   - skip the redzone when initializing a freed heap object, as requested
>     by Qian Cai and Kees Cook
>   - use s->offset to address the freeptr (suggested by Kees Cook)
>   - updated the patch description, added Signed-off-by: tag

v8 failed to incorporate

it's conventional to incorporate such fixes when preparing a new
version of a patch.

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.