[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171101090750.fz3mgz5sefdkgwso@pd.tnic>
Date: Wed, 1 Nov 2017 10:07:50 +0100
From: Borislav Petkov <bp@...en8.de>
To: Kees Cook <keescook@...gle.com>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux-MM <linux-mm@...ck.org>, moritz.lipp@...k.tugraz.at,
daniel.gruss@...k.tugraz.at, michael.schwarz@...k.tugraz.at,
Andy Lutomirski <luto@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Hugh Dickins <hughd@...gle.com>, x86@...nel.org
Subject: Re: [PATCH 23/23] x86, kaiser: add Kconfig
On Tue, Oct 31, 2017 at 04:59:37PM -0700, Kees Cook wrote:
> A quick look through "#ifdef CONFIG_KAISER" looks like it might be
> possible to make this a runtime setting at some point. When doing
> KASLR, it was much more useful to make this runtime selectable so that
> distro kernels could build the support in, but let users decide if
> they wanted to enable it.
Yes please.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists