From: Kees Cook <keescook@chromium.org>
To: speck@linutronix.de
Subject: [MODERATED] [PATCH SSBv11 0/3] seccomp 1
Date: Wed, 2 May 2018 17:44:27 -0700 [thread overview]
Message-ID: <cover.1525308267.git.keescook@chromium.org> (raw)
As seccomp use overlaps best (though not perfectly) with applications
most likely to want speculation flaw mitigations enabled, seccomp will
enable them when seccomp is enabled for a task. Also adds a line to
/proc/$pid/status for examining the mitigation state of a task.
-Kees
Kees Cook (3):
nospec: Allow getting/setting on non-current task
proc: Provide details on speculation flaw mitigations
seccomp: Enable speculation flaw mitigations
arch/x86/kernel/cpu/bugs.c | 27 ++++++++++++++++-----------
fs/proc/array.c | 22 ++++++++++++++++++++++
include/linux/nospec.h | 7 +++++--
kernel/seccomp.c | 18 ++++++++++++++++++
kernel/sys.c | 10 ++++++----
5 files changed, 67 insertions(+), 17 deletions(-)
--
2.17.0
next reply other threads:[~2018-05-03 0:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 0:44 Kees Cook [this message]
2018-05-01 22:07 ` [MODERATED] [PATCH SSBv11 3/3] seccomp 0 Kees Cook
2018-05-01 22:19 ` [MODERATED] [PATCH SSBv11 1/3] seccomp 2 Kees Cook
2018-05-01 22:31 ` [MODERATED] [PATCH SSBv11 2/3] seccomp 3 Kees Cook
2018-05-03 8:58 ` [MODERATED] Re: [PATCH SSBv11 3/3] seccomp 0 Peter Zijlstra
2018-05-03 9:21 ` Thomas Gleixner
2018-05-03 16:03 ` [MODERATED] " Kees Cook
2018-05-03 12:29 ` [MODERATED] Re: [PATCH SSBv11 0/3] seccomp 1 Andi Kleen
2018-05-03 12:45 ` Thomas Gleixner
2018-05-03 14:09 ` [MODERATED] " Ingo Molnar
2018-05-03 14:57 ` Andi Kleen
2018-05-03 17:04 ` Kees Cook
2018-05-03 18:58 ` Andi Kleen
2018-05-03 23:17 ` Kees Cook
2018-05-03 14:47 ` Andi Kleen
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=cover.1525308267.git.keescook@chromium.org \
--to=keescook@chromium.org \
--cc=speck@linutronix.de \
/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.