[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrUNm23OuwM_TuigU9_HFfc2-EopM-Mj9V59Cr5=wRYugA@mail.gmail.com>
Date: Wed, 24 Oct 2018 11:51:38 -0700
From: Andy Lutomirski <luto@...nel.org>
To: "Bae, Chang Seok" <chang.seok.bae@...el.com>
Cc: Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Lutomirski <luto@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>, Andi Kleen <ak@...ux.intel.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"Metzger, Markus T" <markus.t.metzger@...el.com>,
"Ravi V. Shankar" <ravi.v.shankar@...el.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [v3 02/12] x86/fsgsbase/64: Add 'unsafe_fsgsbase' to enable CR4.FSGSBASE
On Tue, Oct 23, 2018 at 11:43 AM Chang S. Bae <chang.seok.bae@...el.com> wrote:
>
> From: Andy Lutomirski <luto@...nel.org>
>
> This is temporary. It will allow the next few patches to be tested
> incrementally.
>
> Setting unsafe_fsgsbase is a root hole. Don't do it.
>
> [ chang: Minor fix. Add the TAINT_INSECURE flag. ]
Reviewed-by: Andy Lutomirski <luto@...nel.org>
although reviewing code that I mostly wrote seems a bit odd...
Powered by blists - more mailing lists