From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: Re: [PATCH] cpu: do not leak vulnerabilities to unprivileged users
Date: Thu, 25 Jan 2018 13:34:33 +0000 [thread overview]
Message-ID: <20180125133433.3a750f25@alans-desktop> (raw)
In-Reply-To: <20180125120401.30596-1-Jason@zx2c4.com>
On Thu, 25 Jan 2018 13:04:01 +0100
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
> While it's public information if the CPU in general has spectre/meltdown
> bugs, it probably shouldn't be as globally obvious to all unprivileged
> users whether or not the kernel is doing something to mitigate
There are plenty of cases where it is useful for an application such as a
JIT to know what level of protection it needs to be providing. For
example if you look across the ecosystem (notably ARM) a lot of common
slower processors are not vulnerable. For those a JIT would want to
generate code without the overhead of any protections.
As you observe any attacker can already trivially ascertain whether
protection is on, so there is no point pretending file permissions
magically stop that. In fact the information is already in cpuinfo.
IMHO given it's trivially available info and useful for JITs it make
sense for the data to be exposed.
Alan
next prev parent reply other threads:[~2018-01-25 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 12:04 Jason A. Donenfeld
2018-01-25 13:34 ` Alan Cox [this message]
2018-01-25 13:40 ` [kernel-hardening] " Jason A. Donenfeld
2018-01-26 12:31 ` [PATCH v2] " Jason A. Donenfeld
2018-01-26 16:43 ` Alan Cox
2018-01-26 17:23 ` [kernel-hardening] " Boris Lukashev
2018-01-26 17:47 ` Jason A. Donenfeld
2018-01-26 18:45 ` Boris Lukashev
2018-01-26 19:07 ` Alan Cox
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=20180125133433.3a750f25@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=Jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-hardening@lists.openwall.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
all inboxes | Powered by JetHome®