linux-kernel - Re: [PATCH 02/10] clockevents: Shutdown and unregister current clockevents at CPUHP_AP_TICK

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

Message-ID: <87ldy4wh9w.ffs@tglx>
Date: Thu, 31 Oct 2024 14:09:31 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Marek Szyprowski <m.szyprowski@...sung.com>, Frederic Weisbecker
 <frederic@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>, Anna-Maria Behnsen
 <anna-maria@...utronix.de>
Subject: Re: [PATCH 02/10] clockevents: Shutdown and unregister current
 clockevents at CPUHP_AP_TICK_DYING

On Thu, Oct 31 2024 at 13:16, Marek Szyprowski wrote:
> On 29.10.2024 13:54, Frederic Weisbecker wrote:
> This patch landed in today's linux-next as commit c80e6e9de6ae 
> ("clockevents: Shutdown and unregister current clockevents at 
> CPUHP_AP_TICK_DYING"). Unfortunately it breaks booting most of my test 
> systems (ARM 32bit, ARM 64bit and RISC-V 64bit). Reverting $subject on 
> top of linux-next (and fixing the merge conflict) seems to be restoring 
> proper boot sequence. Here is a log observed on QEMU's ARM64 'virt' machine:

It's fixed already. Refetch the branch (force updated).

Thanks,

        tglx