All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Scott Bauer <sbauer@eng.utah.edu>
Cc: linux-kernel@vger.kernel.org,
	kernel-hardening@lists.openwall.com, x86@kernel.org,
	luto@amacapital.net, mingo@redhat.com, tglx@linutronix.de,
	wmealing@redhat.com, torvalds@linux-foundation.org,
	Abhiram Balasubramanian <abhiram@cs.utah.edu>,
	Scott Bauer <sbauer@plzdonthack.me>
Subject: [kernel-hardening] Re: [PATCH v4 3/4] Sysctl: SROP Mitigation: Add Sysctl argument to disable SROP.
Date: Tue, 29 Mar 2016 12:59:06 -0700	[thread overview]
Message-ID: <20160329195906.GA9083@tassilo.jf.intel.com> (raw)
In-Reply-To: <1459281207-24377-4-git-send-email-sbauer@eng.utah.edu>

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)

-Andi

WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@linux.intel.com>
To: Scott Bauer <sbauer@eng.utah.edu>
Cc: linux-kernel@vger.kernel.org,
	kernel-hardening@lists.openwall.com, x86@kernel.org,
	luto@amacapital.net, mingo@redhat.com, tglx@linutronix.de,
	wmealing@redhat.com, torvalds@linux-foundation.org,
	Abhiram Balasubramanian <abhiram@cs.utah.edu>,
	Scott Bauer <sbauer@plzdonthack.me>
Subject: Re: [PATCH v4 3/4] Sysctl: SROP Mitigation: Add Sysctl argument to disable SROP.
Date: Tue, 29 Mar 2016 12:59:06 -0700	[thread overview]
Message-ID: <20160329195906.GA9083@tassilo.jf.intel.com> (raw)
In-Reply-To: <1459281207-24377-4-git-send-email-sbauer@eng.utah.edu>

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)

-Andi

  reply	other threads:[~2016-03-29 19:59 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 19:53 [kernel-hardening] [PATCH v4 0/4] SROP Mitigation: Sigreturn Cookies Scott Bauer
2016-03-29 19:53 ` Scott Bauer
2016-03-29 19:53 ` [kernel-hardening] [PATCH v4 1/4] SROP Mitigation: Architecture independent code for signal cookies Scott Bauer
2016-03-29 19:53   ` Scott Bauer
2016-03-29 23:04   ` [kernel-hardening] " Linus Torvalds
2016-03-29 23:04     ` Linus Torvalds
2016-03-31 20:25   ` [kernel-hardening] " Eric W. Biederman
2016-03-31 20:25     ` Eric W. Biederman
2016-03-31 22:00     ` [kernel-hardening] " Linus Torvalds
2016-03-31 22:00       ` Linus Torvalds
2016-03-31 22:17       ` [kernel-hardening] " Eric W. Biederman
2016-03-31 22:17         ` Eric W. Biederman
2016-03-29 19:53 ` [kernel-hardening] [PATCH v4 2/4] x86: SROP Mitigation: Implement Signal Cookies Scott Bauer
2016-03-29 19:53   ` Scott Bauer
2016-03-29 19:53 ` [kernel-hardening] [PATCH v4 3/4] Sysctl: SROP Mitigation: Add Sysctl argument to disable SROP Scott Bauer
2016-03-29 19:53   ` Scott Bauer
2016-03-29 19:59   ` Andi Kleen [this message]
2016-03-29 19:59     ` Andi Kleen
2016-03-29 20:46     ` [kernel-hardening] " Scotty Bauer
2016-03-29 20:46       ` Scotty Bauer
2016-03-29 20:53       ` [kernel-hardening] " Andi Kleen
2016-03-29 20:53         ` Andi Kleen
2016-03-29 19:53 ` [kernel-hardening] [PATCH v4 4/4] Documentation: SROP Mitigation: Add documentation for SROP cookies Scott Bauer
2016-03-29 19:53   ` Scott Bauer
2016-03-29 20:12   ` [kernel-hardening] " Brian Gerst
2016-03-29 20:12     ` Brian Gerst
2016-04-24 16:27   ` [kernel-hardening] " Pavel Machek
2016-04-24 16:27     ` Pavel Machek
2016-03-29 21:29 ` [kernel-hardening] Re: [PATCH v4 0/4] SROP Mitigation: Sigreturn Cookies Andy Lutomirski
2016-03-29 21:29   ` Andy Lutomirski
2016-03-29 21:36   ` [kernel-hardening] " Scotty Bauer
2016-03-29 21:36     ` Scotty Bauer
2016-03-29 21:38     ` [kernel-hardening] " Andy Lutomirski
2016-03-29 21:38       ` Andy Lutomirski
2016-03-29 22:34       ` [kernel-hardening] " Linus Torvalds
2016-03-29 22:34         ` Linus Torvalds
2016-03-29 23:14         ` [kernel-hardening] " Scotty Bauer
2016-03-29 23:14           ` Scotty Bauer
2016-03-31 20:22           ` [kernel-hardening] " Eric W. Biederman
2016-03-31 20:22             ` Eric W. Biederman
2016-04-01 12:57             ` [kernel-hardening] " Cyrill Gorcunov
2016-04-01 12:57               ` Cyrill Gorcunov
2016-03-29 22:55       ` [kernel-hardening] " Daniel Micay
2016-04-24 16:14   ` Pavel Machek
2016-04-24 16:14     ` Pavel Machek
2016-03-29 22:54 ` [kernel-hardening] " Linus Torvalds
2016-03-29 22:54   ` Linus Torvalds
2016-03-29 22:55   ` [kernel-hardening] " Linus Torvalds
2016-03-29 22:55     ` Linus Torvalds
2016-03-29 23:05   ` [kernel-hardening] " Andy Lutomirski
2016-03-29 23:05     ` Andy Lutomirski
2016-03-29 23:11   ` [kernel-hardening] " Scotty Bauer
2016-03-29 23:11     ` Scotty Bauer
2016-03-29 23:25     ` [kernel-hardening] " Linus Torvalds
2016-03-29 23:25       ` Linus Torvalds
2016-03-29 23:34       ` [kernel-hardening] " Scotty Bauer
2016-03-29 23:34         ` Scotty Bauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160329195906.GA9083@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=abhiram@cs.utah.edu \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=sbauer@eng.utah.edu \
    --cc=sbauer@plzdonthack.me \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=wmealing@redhat.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.