linux-kernel - Re: Experiencing freezes with kernel 4.16.3 on a desktop with E5500 CPU (bisect included)

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.1804241105180.5261@nanos.tec.linutronix.de>
Date:   Tue, 24 Apr 2018 11:06:19 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Peter Zijlstra <peterz@...radead.org>
cc:     Diego Viola <diego.viola@...il.com>, linux-kernel@...r.kernel.org,
        len.brown@...el.com, rui.zhang@...el.com,
        "Rafael J. Wysocki" <rjw@...ysocki.net>
Subject: Re: Experiencing freezes with kernel 4.16.3 on a desktop with E5500
 CPU (bisect included)

On Mon, 23 Apr 2018, Peter Zijlstra wrote:

> On Mon, Apr 23, 2018 at 05:58:01PM +0200, Peter Zijlstra wrote:
> > Thomas, we could not find the de-rate stuff, but the above can be
> > simplified; what happens is:
> > 
> > 	cs->flags |= UNSTABLE;
> > 	schedule_work(&watchdog_work)
> > 	  kthread_run(clocksource_watchdog_kthread)
> 
> Also, Thomas, do you remember why we spawn a short running kthread from
> a work ? Can't we simply run the whole thing from the worker thread?

No. I think we did it directly in the early days and then it was changed to
that worker/thread stuff for whatever reason. I need to do git archaeology.

Thanks,

	tglx