From: Kernel User <linux-kernel@riseup.net>
To: linux-kernel@vger.kernel.org
Cc: mhocko@suse.com, x86@kernel.org
Subject: Re: /sys/devices/system/cpu/vulnerabilities/ doesn't show all known CPU vulnerabilities
Date: Wed, 14 Aug 2019 01:00:41 +0300 [thread overview]
Message-ID: <20190814010041.098fe4be@localhost> (raw)
In-Reply-To: <20190813212115.GO16770@zn.tnic>
On Tue, 13 Aug 2019 23:21:15 +0200 Borislav Petkov wrote:
> You have to consider that some of those are addressed by a single
mitigation like MDS
That could be clarified like:
vulnerability1 - mitigation MDS
vulnerability2 - mitigation MDS
vulnerability3 - mitigation 3 (another mitigation)
...
> the mitigation for others like lazy FPU restore is not even present
> in /sys/devices/system/cpu/vulnerabilities/.
Then it could be a file with content saying "No mitigation".
> Also, depending on the CPU, some are not even affected.
That could say "Not affected" (which AFAIK is the case for some cases).
> So maintaining this in the kernel is unnecessary to say the least.
Knowing that there is no mitigation or that a CPU is not affected is
quite different from not knowing anything. So I don't see why you
conclude that knowledge is unnecessary.
next prev parent reply other threads:[~2019-08-13 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 20:28 /sys/devices/system/cpu/vulnerabilities/ doesn't show all known CPU vulnerabilities Kernel User
2019-08-13 21:21 ` Borislav Petkov
2019-08-13 22:00 ` Kernel User [this message]
2019-08-14 7:04 ` Borislav Petkov
2019-08-14 9:11 ` Kernel User
2019-08-15 9:03 ` Thomas Gleixner
2019-08-15 19:37 ` Kernel User
2019-08-15 20:04 ` Thomas Gleixner
2019-08-17 20:41 ` Kernel User
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=20190814010041.098fe4be@localhost \
--to=linux-kernel@riseup.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=x86@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