linux-kernel - Re: x86-tip tsc/tick gripage

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:   Wed, 26 Apr 2017 10:31:54 +0200
From:   Mike Galbraith <efault@....de>
To:     Ingo Molnar <mingo@...nel.org>,
        "Paul E. McKenney" <paulmck@...ibm.com>
Cc:     LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
        Peter Zijlstra <peterz@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: x86-tip tsc/tick gripage

On Wed, 2017-04-26 at 10:21 +0200, Ingo Molnar wrote:

> I have temporarily removed the current timers/urgent lineup from -tip:
> 
>  098991fccfc7: nohz: Print more debug info in tick_nohz_stop_sched_tick()
>  22aa2ad45fd8: tick: Make sure tick timer is active when bypassing reprogramming
>  d58bd60c773d: nohz: Fix again collision between tick and other hrtimers
> 
> ... and have reintegrated tip:master, so it should be back to working I think.
> 
> Does this solve the warning and the RCU stalls on your boxes?

(both boxen building)