linux-kernel - Re: [RFC PATCH] tick/sched: update full_nohz status after SCHED dep is cleared

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: <20200629123651.GA9670@localhost.localdomain>
Date:   Mon, 29 Jun 2020 14:36:51 +0200
From:   Juri Lelli <juri.lelli@...hat.com>
To:     Frederic Weisbecker <frederic@...nel.org>
Cc:     fweisbec@...il.com, tglx@...utronix.de, mingo@...nel.org,
        linux-rt-users@...r.kernel.org, peterz@...radead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] tick/sched: update full_nohz status after SCHED dep
 is cleared

Hi,

On 16/06/20 22:46, Frederic Weisbecker wrote:
> On Tue, Jun 16, 2020 at 08:57:57AM +0200, Juri Lelli wrote:
> > Sure. Let me know if you find anything.
> 
> I managed to reproduce. With "threadirqs" and without
> "tsc=reliable". I see tons of spurious TIMER softirqs.
> Investigation begins! I'll let you know.

Gentle ping. Any new findings about this issue?

Thanks,

Juri