Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options
From: Kees Cook <keescook@xxxxxxxxxxxx>
Date: Thu, 27 Jun 2019 09:23:57 -0700
Cc: Qian Cai <cai@xxxxxx>, Catalin Marinas <catalin.marinas@xxxxxxx>, Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>, Alexander Potapenko <glider@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Christoph Lameter <cl@xxxxxxxxx>, Masahiro Yamada <yamada.masahiro@xxxxxxxxxxxxx>, James Morris <jmorris@xxxxxxxxx>, "Serge E. Hallyn" <serge@xxxxxxxxxx>, Nick Desaulniers <ndesaulniers@xxxxxxxxxx>, Kostya Serebryany <kcc@xxxxxxxxxx>, Dmitry Vyukov <dvyukov@xxxxxxxxxx>, Sandeep Patil <sspatil@xxxxxxxxxxx>, Laura Abbott <labbott@xxxxxxxxxx>, Randy Dunlap <rdunlap@xxxxxxxxxxxxx>, Jann Horn <jannh@xxxxxxxxxx>, Mark Rutland <mark.rutland@xxxxxxx>, Marco Elver <elver@xxxxxxxxxx>, linux-mm@xxxxxxxxx, linux-security-module@xxxxxxxxxxxxxxx, kernel-hardening@xxxxxxxxxxxxxxxxxx, clang-built-linux@xxxxxxxxxxxxxxxx
Delivered-to: mailing list kernel-hardening@xxxxxxxxxxxxxxxxxx
In-reply-to: <20190627061534.GA17798@dhcp22.suse.cz>
Mailing-list: contact kernel-hardening-help@xxxxxxxxxxxxxxxxxx; run by ezmlm

On Thu, Jun 27, 2019 at 08:15:34AM +0200, Michal Hocko wrote:
> This sounds familiar: http://lkml.kernel.org/r/CABXOdTd-cqHM_feAO1tvwn4Z=kM6WHKYAbDJ7LGfMvRPRPG7GA@xxxxxxxxxxxxxx

Your memory is better than mine! I entirely forgot about this and it was
only 2 months ago. Whoops. :P

-- 
Kees Cook

References:
- [PATCH v8 0/3] add init_on_alloc/init_on_free boot options
  - From: Alexander Potapenko
- [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options
  - From: Alexander Potapenko
- Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options
  - From: Qian Cai
- Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options
  - From: Kees Cook
- Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options
  - From: Michal Hocko

Prev by Date: Re: Regarding have kfree() (and related) set the pointer to NULL too
Next by Date: Re: [PATCH v9 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options
Previous by thread: Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options
Next by thread: Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options
Index(es):
- Date
- Thread

[Index of Archives] [Linux Samsung SoC] [Linux Rockchip SoC] [Linux Actions SoC] [Linux for Synopsys ARC Processors] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]