All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 5/5] SSB extra v2 5
Date: Mon, 7 May 2018 17:36:32 -0700	[thread overview]
Message-ID: <20180508003632.GH4050@tassilo.jf.intel.com> (raw)
In-Reply-To: =?utf-8?q?=3C3c3bda6cd68a91d9e79ef1da60d481180d544d20=2E15257?= =?utf-8?q?34796=2Egit=2Edave=2Ehansen=40intel=2Ecom=3E?=

> +	/* To mitigate speculative-store-bypass, we only need
> +	 * mitigation for programs that write to memory.  Mark that
> +	 * the program needs mitigation if loaded without
> +	 * CAP_SYS_ADMIN:
> +	 */
> +	if (env->saw_memory_write && !capable(CAP_SYS_ADMIN))
> +		env->prog->need_mitigation = true;

Flag should have a more descriptive name specific to SSB. 
I bet this won't be the last mitigation needed for EBPF :|

-Andi

  parent reply	other threads:[~2018-05-08  0:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 23:18 [MODERATED] [PATCH 0/5] SSB extra v2 0 Dave Hansen
2018-05-07 23:18 ` [MODERATED] [PATCH 1/5] SSB extra v2 1 Dave Hansen
2018-05-07 23:18 ` [MODERATED] [PATCH 2/5] SSB extra v2 2 Dave Hansen
2018-05-07 23:18 ` [MODERATED] [PATCH 3/5] SSB extra v2 3 Dave Hansen
2018-05-07 23:18 ` [MODERATED] [PATCH 4/5] SSB extra v2 4 Dave Hansen
2018-05-07 23:18 ` [MODERATED] [PATCH 5/5] SSB extra v2 5 Dave Hansen
2018-05-08  0:36 ` Andi Kleen [this message]
2018-05-08  0:46   ` [MODERATED] " Dave Hansen
2018-05-09 15:36     ` Thomas Gleixner
2018-05-09 15:43       ` [MODERATED] " Dave Hansen
2018-05-09 15:55         ` Greg KH
2018-05-09 16:03           ` Dave Hansen
2018-05-09 16:05             ` Jiri Kosina
2018-05-09 16:36               ` Dave Hansen
2018-05-16 15:23                 ` Jon Masters
2018-05-09 21:04         ` Linus Torvalds

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=20180508003632.GH4050@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --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.