linux-kernel - Re: [BUG] Caused by: sched/deadline: Move CPU frequency selection triggering points

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: <20180703113120.55288b03@gandalf.local.home>
Date:   Tue, 3 Jul 2018 11:31:20 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Juri Lelli <juri.lelli@...hat.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Claudio Scordino <claudio@...dence.eu.com>,
        Viresh Kumar <viresh.kumar@...aro.org>,
        Clark Williams <williams@...hat.com>
Subject: Re: [BUG] Caused by: sched/deadline: Move CPU frequency selection
 triggering points

On Tue, 3 Jul 2018 17:07:11 +0200
Juri Lelli <juri.lelli@...hat.com> wrote:

> This got into tip quite recently
> 
> ecda2b66e263 ("sched/deadline: Fix missing clock update")
> 
> could you please double check that you have that in your stack?
> 

Unfortunately, I just tested it out, and it still locks up with this
patch.

Here's more info: I run with my deadline_test with the following
options:

  ./deadline_test  -c 1,2-3 -p 40 -t 9

from https://github.com/rostedt/sched_deadline.git

My box is 1 socket 4 cores and 2 threads each (8 logical CPUS)

Attached is my config.

-- Steve

Download attachment "config" of type "application/octet-stream" (126250 bytes)