Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56FAE98B.8040008@eng.utah.edu>
Date: Tue, 29 Mar 2016 14:46:03 -0600
From: Scotty Bauer <sbauer@....utah.edu>
To: Andi Kleen <ak@...ux.intel.com>
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 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?

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.