linux-kernel - Re: [PATCH 02/18] clocksource/drivers/arch_timer: Workaround for Allwinner A64 timer instability

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>] [day] [month] [year] [list]

Date:   Tue, 26 Feb 2019 20:55:23 -0600
From:   Samuel Holland <samuel@...lland.org>
To:     Sasha Levin <sashal@...nel.org>,
        Daniel Lezcano <daniel.lezcano@...aro.org>, tglx@...utronix.de
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 02/18] clocksource/drivers/arch_timer: Workaround for
 Allwinner A64 timer instability

On 02/26/19 15:23, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
> 
> The bot has tested the following trees: v4.20.12, v4.19.25, v4.14.103, v4.9.160, v4.4.176, v3.18.136.
> 
<snip/>
> 
> How should we proceed with this patch?

This patch is actually only applicable to 4.14.y and newer. It doesn't apply
cleanly because fa8d815fac96 was not backported to 4.14 or 4.19. fa8d815fac96 is
not a dependency, so the extra part of the hunk just needs to be removed.
(Should I send a rebased version somewhere?)

> --
> Thanks,
> Sasha

Cheers,
Samuel