All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: speck@linutronix.de
Subject: [MODERATED] Re: SBB V10 Bundle
Date: Thu, 3 May 2018 07:58:44 +0200	[thread overview]
Message-ID: <20180503055844.mbb5x6uoiu2dy5ri@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1805021508230.1560@nanos.tec.linutronix.de>


* speck for Thomas Gleixner <speck@linutronix.de> wrote:

> > Another question is:
> > 
> > +static int ssb_prctl_set(unsigned long ctrl)
> > +{
> > +       bool rds = !!test_tsk_thread_flag(current, TIF_RDS);
> > +
> > +       if (ssb_mode != SPEC_STORE_BYPASS_PRCTL)
> > +               return -ENXIO;
> > 
> > This might be overly permissive in the 'auto' case which defaulted to 'on', where 
> > an application might still want to disable it for good reasons?
> 
> Permissive? Its restrictive.

I mean when 'auto' set it to 'off', i.e. turned off mitigation. (Darn all the 
negatives ...)

> Also the default is 'prctl' now and I don't think that you want applications
> let override the admin decision, which might be 'on' == global mitigation or
> 'off' == 'no mitigation at all'.

Sure, explicit 'on' and 'off' is an admin choice - but 'auto' isn't really: it's 
the admin saying "whatever you think is right".

> So when the mitigation mode is 'prctl' which is the default then
> applications can fiddle with it. If the admin decided global on or off then
> it's rightfully rejected.
> 
> Hmm?

Correct, the only question is when 'auto' decides 'off' and app uses the prctl().

Do we even care, or do we think if the kernel thinks 'off' is correct then it 
should be forced?

I'd be fine with "we don't care" if "prctl" is the expected distro default.

Thanks,

	Ingo

  reply	other threads:[~2018-05-03  5:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 22:53 SBB V10 Bundle Thomas Gleixner
2018-05-02 11:04 ` [MODERATED] " Ingo Molnar
2018-05-02 12:07 ` Ingo Molnar
2018-05-02 13:23   ` Thomas Gleixner
2018-05-03  5:58     ` Ingo Molnar [this message]
2018-05-03  6:07     ` [MODERATED] " Ingo Molnar
2018-05-03  6:18       ` Thomas Gleixner
2018-05-03  6:27       ` Thomas Gleixner
2018-05-03  6:31         ` Thomas Gleixner

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=20180503055844.mbb5x6uoiu2dy5ri@gmail.com \
    --to=mingo@kernel.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.