From: Ingo Molnar <mingo@kernel.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ben Hutchings <ben@decadent.org.uk>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] cpu/speculation: Warn on unsupported mitigations= parameter
Date: Thu, 16 May 2019 10:16:27 +0200 [thread overview]
Message-ID: <20190516081627.GA109450@gmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1905160947210.22183@cbobk.fhfr.pm>
* Jiri Kosina <jikos@kernel.org> wrote:
> On Thu, 16 May 2019, Geert Uytterhoeven wrote:
>
> > Currently, if the user specifies an unsupported mitigation strategy on
> > the kernel command line, it will be ignored silently. The code will
> > fall back to the default strategy, possibly leaving the system more
> > vulnerable than expected.
>
> Honestly, I am not convinced. We are not doing this for vast majority of
> other cmdline options either, if for any at all.
That's really a weakness - I've been bitten by this previously: I typoed
or mis-remembered a command line option and didn't have it while I
thought I had it.
Our boot-commandline library is pretty user-unfriendly.
Thanks,
Ingo
next prev parent reply other threads:[~2019-05-16 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 7:09 [PATCH] cpu/speculation: Warn on unsupported mitigations= parameter Geert Uytterhoeven
2019-05-16 7:48 ` Jiri Kosina
2019-05-16 8:16 ` Ingo Molnar [this message]
2019-05-16 17:43 ` Josh Poimboeuf
2019-06-26 15:16 ` [tip:smp/urgent] " tip-bot for Geert Uytterhoeven
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=20190516081627.GA109450@gmail.com \
--to=mingo@kernel.org \
--cc=ben@decadent.org.uk \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@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.