[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f24d157-8e8d-b632-0dc5-e082cf4ba8f4@intel.com>
Date: Fri, 13 Jan 2023 11:39:48 -0800
From: Sohil Mehta <sohil.mehta@...el.com>
To: Dave Hansen <dave.hansen@...el.com>,
Yian Chen <yian.chen@...el.com>,
<linux-kernel@...r.kernel.org>, <x86@...nel.org>,
Andy Lutomirski <luto@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Ravi Shankar <ravi.v.shankar@...el.com>,
Tony Luck <tony.luck@...el.com>,
Paul Lai <paul.c.lai@...el.com>,
Kees Cook <keescook@...omium.org>,
Florian Weimer <fweimer@...hat.com>,
Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH 5/7] x86/cpu: Enable LASS (Linear Address Space
Separation)
Adding folks from the previous discussion when a similar suggestion was
made by Kees. There didn't seem to be any major objection that time.
https://lore.kernel.org/lkml/202205111424.DEB0E3418@keescook/
On 1/12/2023 5:17 PM, Sohil Mehta wrote:
> We can make CONFIG_LEGACY_VSYSCALL_NONE as the default instead of the
> current CONFIG_LEGACY_VSYSCALL_XONLY. The kernel can disable LASS at
> boot time if a user/admin has shown explicit preference by selecting
> CONFIG_LEGACY_VSYSCALL_XONLY or by providing command line parameter
> vsyscall=xonly/emulate.
>
> Thoughts?
Powered by blists - more mailing lists