linux-kernel - Re: [PATCH] timers: Fix get_next_timer

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: <b079157aede9b8ebb0cb58a6fdabb7d4d2a84e74.camel@redhat.com>
Date:   Mon, 12 Jul 2021 12:19:00 +0200
From:   Nicolas Saenz Julienne <nsaenzju@...hat.com>
To:     Frederic Weisbecker <frederic@...nel.org>
Cc:     He Zhe <zhe.he@...driver.com>, anna-maria@...utronix.de,
        linux-kernel@...r.kernel.org, tglx@...utronix.de
Subject: Re: [PATCH] timers: Fix get_next_timer_interrupt() with no timers
 pending

On Sat, 2021-07-10 at 02:52 +0200, Frederic Weisbecker wrote:
> Very good catch.
> 
> And the fix looks good:
> 
>     Acked-by: Frederic Weisbecker <frederic@...nel.org>

Thanks!

> 
> I guess later we can turn this .timers_pending into
> .timers_count and that would spare us the costly call to
> __next_timer_interrupt() up to the last level after the last
> timer is dequeued.

Sound like something manageable. I'll probably have a go at it in the future.

-- 
Nicolás Sáenz