From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: [patch 2/6] SSB update 2
Date: Fri, 04 May 2018 15:23:19 +0200 [thread overview]
Message-ID: <20180504132335.673576015@linutronix.de> (raw)
In-Reply-To: 20180504132317.028193533@linutronix.de
Use PR_SPEC_FORCE_DISABLE in seccomp() because seccomp does not allow to
widen restrictions.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
kernel/seccomp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/seccomp.c
+++ b/kernel/seccomp.c
@@ -239,7 +239,7 @@ static inline void spec_mitigate(struct
int state = arch_prctl_spec_ctrl_get(task, which);
if (state > 0 && (state & PR_SPEC_PRCTL))
- arch_prctl_spec_ctrl_set(task, which, PR_SPEC_DISABLE);
+ arch_prctl_spec_ctrl_set(task, which, PR_SPEC_FORCE_DISABLE);
}
static inline void seccomp_assign_mode(struct task_struct *task,
next prev parent reply other threads:[~2018-05-04 13:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 13:23 [patch 0/6] SSB update 0 Thomas Gleixner
2018-05-04 13:23 ` [patch 1/6] SSB update 1 Thomas Gleixner
2018-05-04 13:23 ` Thomas Gleixner [this message]
2018-05-04 13:23 ` [patch 3/6] SSB update 3 Thomas Gleixner
2018-05-04 13:23 ` [patch 4/6] SSB update 4 Thomas Gleixner
2018-05-04 16:25 ` [MODERATED] " Kees Cook
2018-05-04 13:23 ` [patch 5/6] SSB update 5 Thomas Gleixner
2018-05-04 13:23 ` [patch 6/6] SSB update 6 Thomas Gleixner
2018-05-04 16:58 ` [MODERATED] " Kees Cook
2018-05-04 18:42 ` Thomas Gleixner
2018-05-04 13:34 ` [patch 0/6] SSB update 0 Thomas Gleixner
2018-05-04 17:34 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-04 17:52 ` [MODERATED] Is: bikeshedding the bit name (feedback requested)Was:e: " Konrad Rzeszutek Wilk
2018-05-04 23:12 ` Thomas Gleixner
2018-05-07 20:05 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-07 20:10 ` Thomas Gleixner
2018-05-07 21:16 ` [MODERATED] " Konrad Rzeszutek Wilk
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=20180504132335.673576015@linutronix.de \
--to=tglx@linutronix.de \
--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.