From: Alexey Dobriyan <adobriyan@gmail.com>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [patch V2 1/2] sysfs/cpu: Add vulnerability folder
Date: Mon, 8 Jan 2018 21:04:32 +0300 [thread overview]
Message-ID: <20180108180432.GA7668@avx2> (raw)
In-Reply-To: <20180108115454.576dc6ce@alans-desktop>
On Mon, Jan 08, 2018 at 11:54:54AM +0000, Alan Cox wrote:
> On Mon, 8 Jan 2018 08:35:14 +0300
> Alexey Dobriyan <adobriyan@gmail.com> wrote:
>
> > On Sun, Jan 07, 2018 at 10:50:58PM -0500, Konrad Rzeszutek Wilk wrote:
> > > On Mon, Jan 08, 2018 at 01:22:04AM +0300, Alexey Dobriyan wrote:
> > > > Thomas Gleixner wrote:
> > > > > Create /sys/devices/system/cpu/vulnerabilities folder and files for
> > > > > meltdown, spectre_v1 and spectre_v2.
> > > >
> > > > It is called "grep -e '^bugs' /proc/cpuinfo".
> > > >
> > > > kpti is deduceable from .config and /proc/cmdline .
> > > > If people don't know what .config they are running, god bless them.
> > >
> > > It is not just for meltdown (kpti). You also have retpoline and IBRS
> > > which is for spectre.
> >
> > If you, as kernel developer, are sure that bug is properly mitigated
> > to the best of your knowledge then clear the bit from the bug mask.
>
> It's probably useful to have the mitigation status somewhere because that
> is what most people will care about. Both pieces of information are
> needed though.
Then proper way for mainline is Documentation/.
Kernel doesn't announce many things such as ASLR, it simply enables it
by default.
Real checks are done by disassembly and verifying that generated
code does what's necessary anyway. But dumbed down version doesn't need
runtime file in sysfs, internet page somewhere (kernel.org gitweb
interface) should be enough.
next prev parent reply other threads:[~2018-01-08 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 22:22 [patch V2 1/2] sysfs/cpu: Add vulnerability folder Alexey Dobriyan
2018-01-08 3:50 ` Konrad Rzeszutek Wilk
2018-01-08 5:35 ` Alexey Dobriyan
2018-01-08 9:36 ` Thomas Gleixner
2018-01-08 10:30 ` Alexey Dobriyan
2018-01-08 11:54 ` Alan Cox
2018-01-08 18:04 ` Alexey Dobriyan [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-07 21:47 [patch V2 0/2] sysfs/cpu: Implement generic vulnerabilites directory Thomas Gleixner
2018-01-07 21:48 ` [patch V2 1/2] sysfs/cpu: Add vulnerability folder Thomas Gleixner
2018-01-07 22:14 ` Konrad Rzeszutek Wilk
2018-01-08 6:53 ` Greg Kroah-Hartman
2018-01-08 7:29 ` Dominik Brodowski
2018-01-08 7:33 ` Thomas Gleixner
2018-01-26 16:23 ` Andrea Arcangeli
2018-01-26 16:35 ` Greg Kroah-Hartman
2018-01-29 5:30 ` Jon Masters
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=20180108180432.GA7668@avx2 \
--to=adobriyan@gmail.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=konrad@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).