From: Jeremy Linton <jeremy.linton@arm.com> To: linux-arm-kernel@lists.infradead.org Cc: catalin.marinas@arm.com, will.deacon@arm.com, marc.zyngier@arm.com, suzuki.poulose@arm.com, dave.martin@arm.com, shankerd@codeaurora.org, mark.rutland@arm.com, linux-kernel@vger.kernel.org, ykaukab@suse.de, julien.thierry@arm.com, mlangsdo@redhat.com, steven.price@arm.com, Jeremy Linton <jeremy.linton@arm.com>, Thomas Gleixner <tglx@linutronix.de>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, Peter Zijlstra <peterz@infradead.org>, Dave Hansen <dave.hansen@intel.com>, Borislav Petkov <bp@alien8.de>, David Woodhouse <dwmw@amazon.co.uk> Subject: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state Date: Wed, 2 Jan 2019 18:49:15 -0600 [thread overview] Message-ID: <20190103004921.1928921-2-jeremy.linton@arm.com> (raw) In-Reply-To: <20190103004921.1928921-1-jeremy.linton@arm.com> There is a lot of variation in the Arm ecosystem. Because of this, there exist possible cases where the kernel cannot authoritatively determine if a machine is vulnerable. Rather than guess the vulnerability status in cases where the mitigation is disabled or the firmware isn't responding correctly, we need to display an "Unknown" state. Signed-off-by: Jeremy Linton <jeremy.linton@arm.com> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Dave Hansen <dave.hansen@intel.com> Cc: Borislav Petkov <bp@alien8.de> Cc: David Woodhouse <dwmw@amazon.co.uk> --- Documentation/ABI/testing/sysfs-devices-system-cpu | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu index 9605dbd4b5b5..876103fddfa4 100644 --- a/Documentation/ABI/testing/sysfs-devices-system-cpu +++ b/Documentation/ABI/testing/sysfs-devices-system-cpu @@ -495,6 +495,7 @@ Description: Information about CPU vulnerabilities "Not affected" CPU is not affected by the vulnerability "Vulnerable" CPU is affected and no mitigation in effect "Mitigation: $M" CPU is affected and mitigation $M is in effect + "Unknown" The kernel is unable to make a determination Details about the l1tf file can be found in Documentation/admin-guide/l1tf.rst -- 2.17.2
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Linton <jeremy.linton@arm.com> To: linux-arm-kernel@lists.infradead.org Cc: mark.rutland@arm.com, mlangsdo@redhat.com, "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, suzuki.poulose@arm.com, marc.zyngier@arm.com, catalin.marinas@arm.com, Dave Hansen <dave.hansen@intel.com>, julien.thierry@arm.com, will.deacon@arm.com, linux-kernel@vger.kernel.org, Jeremy Linton <jeremy.linton@arm.com>, steven.price@arm.com, Peter Zijlstra <peterz@infradead.org>, Borislav Petkov <bp@alien8.de>, David Woodhouse <dwmw@amazon.co.uk>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, ykaukab@suse.de, Thomas Gleixner <tglx@linutronix.de>, dave.martin@arm.com, shankerd@codeaurora.org Subject: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state Date: Wed, 2 Jan 2019 18:49:15 -0600 [thread overview] Message-ID: <20190103004921.1928921-2-jeremy.linton@arm.com> (raw) In-Reply-To: <20190103004921.1928921-1-jeremy.linton@arm.com> There is a lot of variation in the Arm ecosystem. Because of this, there exist possible cases where the kernel cannot authoritatively determine if a machine is vulnerable. Rather than guess the vulnerability status in cases where the mitigation is disabled or the firmware isn't responding correctly, we need to display an "Unknown" state. Signed-off-by: Jeremy Linton <jeremy.linton@arm.com> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Dave Hansen <dave.hansen@intel.com> Cc: Borislav Petkov <bp@alien8.de> Cc: David Woodhouse <dwmw@amazon.co.uk> --- Documentation/ABI/testing/sysfs-devices-system-cpu | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu index 9605dbd4b5b5..876103fddfa4 100644 --- a/Documentation/ABI/testing/sysfs-devices-system-cpu +++ b/Documentation/ABI/testing/sysfs-devices-system-cpu @@ -495,6 +495,7 @@ Description: Information about CPU vulnerabilities "Not affected" CPU is not affected by the vulnerability "Vulnerable" CPU is affected and no mitigation in effect "Mitigation: $M" CPU is affected and mitigation $M is in effect + "Unknown" The kernel is unable to make a determination Details about the l1tf file can be found in Documentation/admin-guide/l1tf.rst -- 2.17.2 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-03 0:49 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-03 0:49 [PATCH v2 0/7] add system vulnerability sysfs entries Jeremy Linton 2019-01-03 0:49 ` Jeremy Linton 2019-01-03 0:49 ` Jeremy Linton [this message] 2019-01-03 0:49 ` [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state Jeremy Linton 2019-01-03 9:38 ` Greg Kroah-Hartman 2019-01-03 9:38 ` Greg Kroah-Hartman 2019-01-03 16:38 ` Jeremy Linton 2019-01-03 16:38 ` Jeremy Linton 2019-01-03 16:48 ` Greg Kroah-Hartman 2019-01-03 16:48 ` Greg Kroah-Hartman 2019-01-04 14:08 ` Dave Martin 2019-01-04 14:08 ` Dave Martin 2019-01-04 14:18 ` Greg Kroah-Hartman 2019-01-04 14:18 ` Greg Kroah-Hartman 2019-01-04 14:55 ` Will Deacon 2019-01-04 14:55 ` Will Deacon 2019-01-03 16:37 ` Dave Martin 2019-01-03 16:37 ` Dave Martin 2019-01-03 16:46 ` Jeremy Linton 2019-01-03 16:46 ` Jeremy Linton 2019-01-03 19:30 ` Stefan Wahren 2019-01-03 19:30 ` Stefan Wahren 2019-01-03 20:32 ` Jeremy Linton 2019-01-03 20:32 ` Jeremy Linton 2019-01-04 10:13 ` Will Deacon 2019-01-04 10:13 ` Will Deacon 2019-01-03 0:49 ` [PATCH v2 2/7] arm64: kpti: move check for non-vulnerable CPUs to a function Jeremy Linton 2019-01-03 0:49 ` Jeremy Linton 2019-01-03 0:49 ` [PATCH v2 3/7] arm64: add sysfs vulnerability show for meltdown Jeremy Linton 2019-01-03 0:49 ` Jeremy Linton 2019-01-03 0:49 ` [PATCH v2 4/7] arm64: add sysfs vulnerability show for spectre v1 Jeremy Linton 2019-01-03 0:49 ` Jeremy Linton 2019-01-03 0:49 ` [PATCH v2 5/7] arm64: add sysfs vulnerability show for spectre v2 Jeremy Linton 2019-01-03 0:49 ` Jeremy Linton 2019-01-03 0:49 ` [PATCH v2 6/7] arm64: add sysfs vulnerability show for speculative store bypass Jeremy Linton 2019-01-03 0:49 ` Jeremy Linton 2019-01-03 0:49 ` [PATCH v2 7/7] arm64: enable generic CPU vulnerabilites support Jeremy Linton 2019-01-03 0:49 ` Jeremy Linton
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=20190103004921.1928921-2-jeremy.linton@arm.com \ --to=jeremy.linton@arm.com \ --cc=bp@alien8.de \ --cc=catalin.marinas@arm.com \ --cc=dave.hansen@intel.com \ --cc=dave.martin@arm.com \ --cc=dwmw@amazon.co.uk \ --cc=gregkh@linuxfoundation.org \ --cc=julien.thierry@arm.com \ --cc=konrad.wilk@oracle.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=marc.zyngier@arm.com \ --cc=mark.rutland@arm.com \ --cc=mlangsdo@redhat.com \ --cc=peterz@infradead.org \ --cc=rafael.j.wysocki@intel.com \ --cc=shankerd@codeaurora.org \ --cc=steven.price@arm.com \ --cc=suzuki.poulose@arm.com \ --cc=tglx@linutronix.de \ --cc=will.deacon@arm.com \ --cc=ykaukab@suse.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.