linux-kernel - Re: [PATCH AUTOSEL 4.14 10/21] ARM: make lookup_processor_type() non-_

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20181128141252.GB131942@sasha-vm>
Date:   Wed, 28 Nov 2018 09:12:52 -0500
From:   Sasha Levin <sashal@...nel.org>
To:     Russell King - ARM Linux <linux@...linux.org.uk>
Cc:     stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 4.14 10/21] ARM: make lookup_processor_type()
 non-__init

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.

>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?

--
Thanks,
Sasha