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 v2] cpu: do not leak vulnerabilities to unprivileged users
Date: Fri, 26 Jan 2018 16:43:10 +0000 [thread overview]
Message-ID: <20180126164310.13a29ad2@alans-desktop> (raw)
In-Reply-To: <20180126123158.9575-1-Jason@zx2c4.com>
On Fri, 26 Jan 2018 13:31:58 +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
As I replied to you last time you posted this
a) The info is already trivially accessible via /proc/cpuinfo or by
measurement to an attacker
b) Some JIT and other environments need to know
Alan
next prev parent reply other threads:[~2018-01-26 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 12:04 [PATCH] " Jason A. Donenfeld
2018-01-25 13:34 ` Alan Cox
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 [this message]
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=20180126164310.13a29ad2@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®