linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Artem S. Tashkinov" <aros@gmx.com>
To: linux-kernel@vger.kernel.org
Subject: Disabling CPU vulnerabilities workarounds
Date: Sat, 25 Aug 2018 10:42:37 +0000	[thread overview]
Message-ID: <575b6581-7dcb-96a9-b06e-9f74dda5fa86@gmx.com> (raw)

Hello LKML,

As time goes by more and more fixes of Intel/AMD/ARM CPUs 
vulnerabilities are added to the Linux kernel without a simple way to 
disable them all in one fell swoop.

Disabling is a good option for strictly confined environments where no 
3d party untrusted code is ever to be run, e.g. a rendering farm, a 
supercomputer, or even a home server which runs Samba/SSH server and 
nothing else.

I wonder if someone could wrote a patch which implemented the following 
two options for the kernel:

* A boot option option which allows to disable most runtime 
protections/workarounds/fixes (as far as I understand some of them can't 
be reverted since they are compiled in or use certain GCC flags), e.g. 
let's call it "insecure" or "insecurecpumode".

* A compile-time CONFIG_ option which disables all these fixes 
_permanently_ without a way to turn them later back on during runtime.

Right now linux/Documentation/admin-guide/kernel-parameters.txt is a 
mess of various things which take ages to sift through and there's zero 
understanding whether you've found everything and correctly disabled it.


Best regards,
Artem

             reply	other threads:[~2018-08-25 10:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-25 10:42 Artem S. Tashkinov [this message]
2018-08-25 18:39 ` Disabling CPU vulnerabilities workarounds Casey Schaufler
2018-08-25 23:28   ` Artem S. Tashkinov
2018-08-26 20:54     ` Casey Schaufler
  -- strict thread matches above, loose matches on Subject: below --
2018-08-23 16:33 Artem S. Tashkinov

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=575b6581-7dcb-96a9-b06e-9f74dda5fa86@gmx.com \
    --to=aros@gmx.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).