linux-kernel - Sv: Sv: [PATCH] hrtimer: Interrupt storm on clock

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: <20210225111814.8383-1-mikael.beckius@windriver.com>
Date:   Thu, 25 Feb 2021 12:18:14 +0100
From:   Mikael Beckius <mikael.beckius@...driver.com>
To:     anna-maria@...utronix.de
Cc:     linux-kernel@...r.kernel.org, mikael.beckius@...driver.com,
        tglx@...utronix.de
Subject: Sv: Sv: [PATCH] hrtimer: Interrupt storm on clock_settime

> The proposed change breaks the reprogramming logic. To keep it working
> cpu_base::*expires_next is only updated by hrtimer_reprogram() and
> hrtimer_interrupt(). I will send you a patch for testing in reply to this
> thread. The patch is compile tested only.
> 
Ok. I kind of guessed that would be the response as I noticed a similar comment
during the review of the original patch which introduced the softirq_expires_next
logic. Anyway it seemed logical to update softirq_expires_next
when updating softirq_next_timer.

Micke