[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160329205322.GB9083@tassilo.jf.intel.com>
Date: Tue, 29 Mar 2016 13:53:22 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Scotty Bauer <sbauer@....utah.edu>
Cc: linux-kernel@...r.kernel.org, kernel-hardening@...ts.openwall.com,
x86@...nel.org, luto@...capital.net, mingo@...hat.com,
tglx@...utronix.de, wmealing@...hat.com,
torvalds@...ux-foundation.org,
Abhiram Balasubramanian <abhiram@...utah.edu>,
Scott Bauer <sbauer@...donthack.me>
Subject: Re: [PATCH v4 3/4] Sysctl: SROP Mitigation: Add Sysctl argument to
disable SROP.
On Tue, Mar 29, 2016 at 02:46:03PM -0600, Scotty Bauer wrote:
>
>
>
> On 03/29/2016 01:59 PM, Andi Kleen wrote:
> > On Tue, Mar 29, 2016 at 01:53:26PM -0600, Scott Bauer wrote:
> >> This patch adds a sysctl argument to disable SROP protection.
> >
> > Sysctl needs to be documented in Documentation/sysctl/
> >
> > Also negated sysctl is weird, normally they are positive (enable-xxx)
> >
>
> Sure, I can change it. This may be a dumb question: I want SROP to be enabled by default, and thus the new
> enable-xxx will be initialized to 1, that's fine, right?
Yes that's fine.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only
Powered by blists - more mailing lists