All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Alexander Potapenko <glider@google.com>, akpm@linux-foundation.org
Cc: linux-security-module@vger.kernel.org, linux-mm@kvack.org,
	ndesaulniers@google.com, kcc@google.com, dvyukov@google.com,
	keescook@chromium.org, sspatil@android.com, labbott@redhat.com,
	kernel-hardening@lists.openwall.com
Subject: Re: [PATCH] mm: security: introduce CONFIG_INIT_HEAP_ALL
Date: Tue, 16 Apr 2019 10:30:20 +0200	[thread overview]
Message-ID: <35935775-1c0d-6016-5bb3-0abee65a7492@suse.cz> (raw)
In-Reply-To: <20190412124501.132678-1-glider@google.com>

On 4/12/19 2:45 PM, Alexander Potapenko wrote:
> +config INIT_HEAP_ALL
> +	bool "Initialize kernel heap allocations"

Calling slab and page allocations together as "heap" is rather uncommon
in the kernel I think. But I don't have a better word right now.

> +	default n
> +	help
> +	  Enforce initialization of pages allocated from page allocator
> +	  and objects returned by kmalloc and friends.
> +	  Allocated memory is initialized with zeroes, preventing possible
> +	  information leaks and making the control-flow bugs that depend
> +	  on uninitialized values more deterministic.
> +
>  config GCC_PLUGIN_STRUCTLEAK_VERBOSE
>  	bool "Report forcefully initialized variables"
>  	depends on GCC_PLUGIN_STRUCTLEAK
> 


  parent reply	other threads:[~2019-04-16  8:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 12:45 [PATCH] mm: security: introduce CONFIG_INIT_HEAP_ALL Alexander Potapenko
2019-04-12 12:45 ` Alexander Potapenko
2019-04-12 14:16 ` Qian Cai
2019-04-12 14:16   ` Qian Cai
2019-04-12 15:23   ` Alexander Potapenko
2019-04-12 15:23     ` Alexander Potapenko
2019-04-16  2:02 ` Andrew Morton
2019-04-16  8:33   ` Vlastimil Babka
2019-04-16 12:21   ` Alexander Potapenko
2019-04-16 12:21     ` Alexander Potapenko
2019-04-16  8:30 ` Vlastimil Babka [this message]
2019-04-16 12:04   ` Alexander Potapenko
2019-04-16 12:04     ` Alexander Potapenko
2019-04-16 15:32 ` Christopher Lameter
2019-04-16 15:32   ` Christopher Lameter
2019-04-16 16:01   ` Alexander Potapenko
2019-04-16 16:01     ` Alexander Potapenko
2019-04-16 16:30     ` Christopher Lameter
2019-04-16 16:30       ` Christopher Lameter
2019-04-17 11:03       ` Alexander Potapenko
2019-04-17 11:03         ` Alexander Potapenko
2019-04-17 17:04         ` Alexander Potapenko
2019-04-17 17:04           ` Alexander Potapenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35935775-1c0d-6016-5bb3-0abee65a7492@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=kcc@google.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=labbott@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=sspatil@android.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.