mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Kernel User <linux-kernel@riseup.net>
Cc: LKML <linux-kernel@vger.kernel.org>, mhocko@suse.com, x86@kernel.org
Subject: Re: /sys/devices/system/cpu/vulnerabilities/ doesn't show all known CPU vulnerabilities
Date: Thu, 15 Aug 2019 11:03:35 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1908151054090.2241@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190814121154.12f488f7@localhost>

On Wed, 14 Aug 2019, Kernel User wrote:
> On Wed, 14 Aug 2019 09:04:57 +0200 Borislav Petkov wrote:
> 
> > IMO, what you want does not belong in sysfs but in documentation.
> 
> How would documentation (a fixed static text file) tell whether a
> particular system is vulnerable or not?
> 
> > I partially see your point that a table of sorts mapping all those CPU
> > vulnerability names to (possible) mitigations is needed for users
> > which would like to know whether they're covered, without having to
> > run some scripts from github,
> 
> Correct.
> 
> > but sysfs just ain't the place.
> 
> Then why is it currently used for some of the vulnerabilities?

It's used to denote vulnerability classes and their mitigations:

  - Spectre v1
  - Spectre v2
  - Meltdown
  - SSB
  - L1TF
  - MDS

We are not tracking subclasses and their individual CVEs. The sysfs
interface is accurate (including SMT state) and the mapping to subclasses
and CVEs can be done by user space tools if required.

Thanks,

	tglx

  reply	other threads:[~2019-08-15  9:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13 20:28 Kernel User
2019-08-13 21:21 ` Borislav Petkov
2019-08-13 22:00   ` Kernel User
2019-08-14  7:04     ` Borislav Petkov
2019-08-14  9:11       ` Kernel User
2019-08-15  9:03         ` Thomas Gleixner [this message]
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=alpine.DEB.2.21.1908151054090.2241@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=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

all inboxes | Powered by JetHome®