lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 23 Dec 2018 15:58:38 -0800 (PST) From: David Miller <davem@...emloft.net> To: alexei.starovoitov@...il.com Cc: gustavo@...eddedor.com, ast@...nel.org, daniel@...earbox.net, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] net: core: Fix Spectre v1 vulnerability From: Alexei Starovoitov <alexei.starovoitov@...il.com> Date: Sat, 22 Dec 2018 22:00:00 -0800 > On Sat, Dec 22, 2018 at 11:03:31PM -0600, Gustavo A. R. Silva wrote: >> > I took another look at the following patches: >> > "net: core: Fix Spectre v1 vulnerability" >> > "nfc: af_nfc: Fix Spectre v1 vulnerability" >> > "can: af_can: Fix Spectre v1 vulnerability" >> > and I have to say that none of them are necessary. >> > I'm not sure whether there were other patches that pretend to fix spectre1. ... > in other words there is no bug and there is no vulnerability, > but there is a 'policy' set by ... ? > So hence Nack to the policy and Nack to the patches. I have to agree with Alexei after looking at all of this stuff one more time. I'm reverting all of these changes.
Powered by blists - more mailing lists