[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1711021923020.2824@nanos>
Date: Thu, 2 Nov 2017 19:24:32 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Andy Lutomirski <luto@...capital.net>
cc: Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
moritz.lipp@...k.tugraz.at,
Daniel Gruss <daniel.gruss@...k.tugraz.at>,
michael.schwarz@...k.tugraz.at, Kees Cook <keescook@...gle.com>,
Hugh Dickins <hughd@...gle.com>, X86 ML <x86@...nel.org>
Subject: Re: [PATCH 02/23] x86, kaiser: do not set _PAGE_USER for init_mm
page tables
On Thu, 2 Nov 2017, Andy Lutomirski wrote:
> > On Nov 2, 2017, at 5:38 PM, Dave Hansen <dave.hansen@...ux.intel.com> wrote:
> >
> >> On 11/02/2017 04:33 AM, Thomas Gleixner wrote:
> >> So for the problem at hand, I'd suggest we disable the vsyscall stuff if
> >> CONFIG_KAISER=y and be done with it.
> >
> > Just to be clear, are we suggesting to just disable
> > LEGACY_VSYSCALL_NATIVE if KAISER=y, and allow LEGACY_VSYSCALL_EMULATE?
> > Or, do we just force LEGACY_VSYSCALL_NONE=y?
>
> We'd have to force NONE, and Linus won't like it.
The much I hate it, I already accepted grudgingly that we have to keep it
alive in some way or the other.
Thanks,
tglx
Powered by blists - more mailing lists