linux-kernel - Re: kworker/0:3+pm hogging CPU

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: <20200901152728.GI16650@dhcp22.suse.cz>
Date:   Tue, 1 Sep 2020 17:27:28 +0200
From:   Michal Hocko <mhocko@...e.com>
To:     Mathias Nyman <mathias.nyman@...ux.intel.com>
Cc:     Alan Stern <stern@...land.harvard.edu>,
        Salvatore Bonaccorso <carnil@...ian.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Greg KH <gregkh@...uxfoundation.org>,
        linux-usb@...r.kernel.org, "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Dirk Kostrewa <dirk.kostrewa@...lbox.org>
Subject: Re: kworker/0:3+pm hogging CPU

On Mon 31-08-20 14:37:10, Mathias Nyman wrote:
[...]
> I can't come up with any good solution to this right now.
> Only bad ideas such as
> a. Add a sleep to the over-current case, 
>    doesn't solve anything else than the ~100% cpu hogging part of the problem 

This sounds like a better thing from the user space point of view. I do
not have any insight on what kind of other side effects this might have
so I didn't dare to try that on my piece of (broken) HW. I do not see
the problem all the time and I plan to replace it soon anyway.

Considering that tweaking the power management helps maybe that could be
done automagically after many consecutive failures.

Just my 2c
-- 
Michal Hocko
SUSE Labs