Message-Id: <20180504132317.028193533@linutronix.de>
Date: Fri, 04 May 2018 15:23:17 +0200
From: Thomas Gleixner <tglx@linutronix.de>
Subject: [patch 0/6] SSB update 0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
To: speck@linutronix.de

Following up to the discussion about seccomp and enforced mitigation and
after Andi clarifying his concerns (Thanks Andi!), Kees and myself came up
with the following solution:

1) Add a PRCTL control which allows to force disable mitigation. Once set
   this cannot be undone anymore.

2) Make seccomp use that new control because the seccomp semantics do not
   allow to widen restrictions after they have been applied.

3) Add a seccomp filter flag which allows seccomp users to opt out of the
   mitigation enforcement. This has no effect when the mitigation has been
   enforced globally or via the prctl before.

4) Add a migitation option for the command line "seccomp" which enables the
   seccomp mechanism plus the prctl. Selecting "prctl" disables the seccomp
   mechanism

5) Make "seccomp" the default mitigation mode for now.

Applies on top of the master branch. Git bundle follows in separate mail.

Thanks,

	tglx