|
Message-ID: <lsq.1520823972.995550615@decadent.org.uk> Date: Mon, 12 Mar 2018 03:06:12 +0000 From: Ben Hutchings <ben@...adent.org.uk> To: linux-kernel@...r.kernel.org, stable@...r.kernel.org CC: akpm@...ux-foundation.org, linux-arch@...r.kernel.org, gregkh@...uxfoundation.org, "Dan Williams" <dan.j.williams@...el.com>, alan@...ux.intel.com, "Thomas Gleixner" <tglx@...utronix.de>, torvalds@...ux-foundation.org, "Jiri Slaby" <jslaby@...e.cz>, kernel-hardening@...ts.openwall.com Subject: [PATCH 3.16 59/76] x86/spectre: Report get_user mitigation for spectre_v1 3.16.56-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Dan Williams <dan.j.williams@...el.com> commit edfbae53dab8348fca778531be9f4855d2ca0360 upstream. Reflect the presence of get_user(), __get_user(), and 'syscall' protections in sysfs. The expectation is that new and better tooling will allow the kernel to grow more usages of array_index_nospec(), for now, only claim mitigation for __user pointer de-references. Reported-by: Jiri Slaby <jslaby@...e.cz> Signed-off-by: Dan Williams <dan.j.williams@...el.com> Signed-off-by: Thomas Gleixner <tglx@...utronix.de> Cc: linux-arch@...r.kernel.org Cc: kernel-hardening@...ts.openwall.com Cc: gregkh@...uxfoundation.org Cc: torvalds@...ux-foundation.org Cc: alan@...ux.intel.com Link: https://lkml.kernel.org/r/151727420158.33451.11658324346540434635.stgit@dwillia2-desk3.amr.corp.intel.com Signed-off-by: Ben Hutchings <ben@...adent.org.uk> --- arch/x86/kernel/cpu/bugs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/arch/x86/kernel/cpu/bugs.c +++ b/arch/x86/kernel/cpu/bugs.c @@ -353,7 +353,7 @@ ssize_t cpu_show_spectre_v1(struct devic { if (!boot_cpu_has_bug(X86_BUG_SPECTRE_V1)) return sprintf(buf, "Not affected\n"); - return sprintf(buf, "Vulnerable\n"); + return sprintf(buf, "Mitigation: __user pointer sanitization\n"); } ssize_t cpu_show_spectre_v2(struct device *dev,
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.