[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e5ccf92-cc58-ab2b-d025-0f5642d5f4a6@infradead.org>
Date: Wed, 8 May 2019 18:04:55 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Alexander Potapenko <glider@...gle.com>, akpm@...ux-foundation.org,
cl@...ux.com, keescook@...omium.org, labbott@...hat.com
Cc: linux-mm@...ck.org, linux-security-module@...r.kernel.org,
kernel-hardening@...ts.openwall.com, yamada.masahiro@...ionext.com,
jmorris@...ei.org, serge@...lyn.com, ndesaulniers@...gle.com,
kcc@...gle.com, dvyukov@...gle.com, sspatil@...roid.com, jannh@...gle.com,
mark.rutland@....com
Subject: Re: [PATCH 1/4] mm: security: introduce init_on_alloc=1 and
init_on_free=1 boot options
On 5/8/19 8:37 AM, Alexander Potapenko wrote:
> diff --git a/security/Kconfig.hardening b/security/Kconfig.hardening
> index 0a1d4ca314f4..4a4001f5ad25 100644
> --- a/security/Kconfig.hardening
> +++ b/security/Kconfig.hardening
> @@ -159,6 +159,22 @@ config STACKLEAK_RUNTIME_DISABLE
> runtime to control kernel stack erasing for kernels built with
> CONFIG_GCC_PLUGIN_STACKLEAK.
>
> +config INIT_ON_ALLOC_DEFAULT_ON
> + bool "Set init_on_alloc=1 by default"
> + default false
That should be spelled "default n" but since that is already the default,
just omit the line completely.
> + help
> + Enable init_on_alloc=1 by default, making the kernel initialize every
> + page and heap allocation with zeroes.
> + init_on_alloc can be overridden via command line.
> +
> +config INIT_ON_FREE_DEFAULT_ON
> + bool "Set init_on_free=1 by default"
> + default false
ditto.
> + help
> + Enable init_on_free=1 by default, making the kernel initialize freed
> + pages and slab memory with zeroes.
> + init_on_free can be overridden via command line.
> +
> endmenu
>
> endmenu
--
~Randy
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.
