linux-kernel - Re: [PATCH 1/2] nohz: Fix again collision between tick and other hrtimers

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]

Date:   Thu, 20 Apr 2017 12:00:06 -0400
From:   Rik van Riel <riel@...hat.com>
To:     Frederic Weisbecker <fweisbec@...il.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...nel.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        James Hartsock <hartsjc@...hat.com>, stable@...r.kernel.org,
        Tim Wright <tim@...bash.co.uk>, Pavel Machek <pavel@....cz>
Subject: Re: [PATCH 1/2] nohz: Fix again collision between tick and other
 hrtimers

On Thu, 2017-04-20 at 17:30 +0200, Frederic Weisbecker wrote:
> (This restores commit 24b91e360ef521a2808771633d76ebc68bd5604b that
> got
> reverted by commit 558e8e27e73f53f8a512485be538b07115fe5f3c due to a
> regression where CPUs spuriously stopped ticking. The issue happened
> when a tick fired too early past its expected expiration: on IRQ exit
> the tick was scheduled again to the same deadline but skipped
> reprogramming because ts->next_tick still kept in cache the deadline.
> This has been fixed now with resetting ts->next_tick from the tick
> itself. Extra care has also been taken to prevent from obsolete
> values
> throughout CPU hotplug operations.)
> 
Acked-by: Rik van Riel <riel@...hat.com>