On Wed, Nov 28, 2018 at 09:12:52AM -0500, Sasha Levin wrote: > On Fri, Nov 23, 2018 at 12:02:54AM +0000, Russell King - ARM Linux wrote: > >Hi Sasha, > > > >We need to keep track of which Spectre patches have been backported > >and which haven't. David Long has been doing the backport work, > >which doesn't include all the patches in my present spectre branch. > >You've picked up the last five, meaning there's a bunch in the middle > >of the entire series which haven't yet been considered - for example, > >the Spectre variant 1.1 patches. > > I'll drop all the ones you pointed out from my branches. Sometimes it's > difficult to tell if a certain patch is part of the spectre fix. Given that all the 32-bit ARM Spectre patches are sequential in a branch, it shouldn't be too difficult as it's possible to list all the commit IDs using: $ git rev-list v4.16..383fb3ee8024 where 383fb3ee8024 is the current head. I'm not anticipating at this time anything further. > >The entire series of 32-bit ARM Spectre patches can be listed in > >mainline via: > > > >$ git log v4.16..383fb3ee8024 > > > >where almost all of those need to be applied to stable kernels, with > >possible manual back-porting where they don't apply. > > Is it something that will be backported at some point? Yes, as I mentioned, this is work that David Long is undertaking, with a separate review process before submitting the backported patches for inclusion in the appropriate stable tree. -- RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up
