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: <alpine.LNX.2.21.1.2001170929550.255@nippy.intranet>
Date:   Fri, 17 Jan 2020 10:21:26 +1100 (AEDT)
From:   Finn Thain <fthain@...egraphics.com.au>
To:     Sasha Levin <sashal@...nel.org>
cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        linux-m68k@...ts.linux-m68k.org
Subject: Re: [PATCH AUTOSEL 4.4 064/174] m68k: mac: Fix VIA timer counter
 accesses


On Thu, 16 Jan 2020, Sasha Levin wrote:

> From: Finn Thain <fthain@...egraphics.com.au>
> 
> [ Upstream commit 0ca7ce7db771580433bf24454f7a1542bd326078 ]
> 

This commit has been selected for 4.4, 4.9, 4.14 and 4.19. But this commit 
has questionable value without it's parent, commit 1efdd4bd2543 ("m68k: 
Call timer_interrupt() with interrupts disabled").

For all stable branches, I'd prefer you selected both commits or neither, 
because I periodically backport to a branch based on stable/linux-4.14.y.

Thanks.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ