From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Gustavo A. R. Silva" Subject: Re: [PATCH] net: core: Fix Spectre v1 vulnerability Date: Sun, 23 Dec 2018 18:01:35 -0600 Message-ID: <31dc24bd-ef31-6db4-d1b7-10f9d6619843@embeddedor.com> References: <20181223041253.bxqru567rs32mecg@ast-mbp.dhcp.thefacebook.com> <20181223055959.jlzbyd5ec55thiz7@ast-mbp.dhcp.thefacebook.com> <20181223.155838.90910738750758535.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: David Miller , alexei.starovoitov@gmail.com Return-path: In-Reply-To: <20181223.155838.90910738750758535.davem@davemloft.net> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 12/23/18 5:58 PM, David Miller wrote: > From: Alexei Starovoitov > 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. > Yeah. That's fine with me. Thanks -- Gustavo