Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754849AbeAHSEi (ORCPT + 1 other); Mon, 8 Jan 2018 13:04:38 -0500 Received: from mail-wm0-f66.google.com ([74.125.82.66]:39592 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754131AbeAHSEg (ORCPT ); Mon, 8 Jan 2018 13:04:36 -0500 X-Google-Smtp-Source: ACJfBoskdlJktORzl+ymBINtdIuCARAvYRqGU2cWUY4bMJeWEaufNqPdAdDW2IirHDpOzmUp9i3sgQ== Date: Mon, 8 Jan 2018 21:04:32 +0300 From: Alexey Dobriyan To: Alan Cox Cc: Konrad Rzeszutek Wilk , tglx@linutronix.de, linux-kernel@vger.kernel.org Subject: Re: [patch V2 1/2] sysfs/cpu: Add vulnerability folder Message-ID: <20180108180432.GA7668@avx2> References: <20180107222204.GA28038@avx2> <20180108035056.GA6599@localhost.localdomain> <20180108053514.GA2408@avx2> <20180108115454.576dc6ce@alans-desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180108115454.576dc6ce@alans-desktop> User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Mon, Jan 08, 2018 at 11:54:54AM +0000, Alan Cox wrote: > On Mon, 8 Jan 2018 08:35:14 +0300 > Alexey Dobriyan 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.