linux-kernel - Re: [rht_deferred_worker] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 62s!

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] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 27 Nov 2017 13:32:59 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Fengguang Wu <fengguang.wu@...el.com>
Cc:     Network Development <netdev@...r.kernel.org>,
        Thomas Graf <tgraf@...g.ch>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        "David S. Miller" <davem@...emloft.net>,
        Florian Westphal <fw@...len.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        LKP <lkp@...org>
Subject: Re: [rht_deferred_worker] BUG: workqueue lockup - pool cpus=0 node=0
 flags=0x0 nice=0 stuck for 62s!

On Tue, Nov 21, 2017 at 3:19 AM, Fengguang Wu <fengguang.wu@...el.com> wrote:
>
> FYI this happens in mainline kernel 4.14.0-10859-gcf9b077.
> It at least dates back to v4.5 .

Hmm. This seems to be doing some concurrent rhashtable stress testing,
while at the same time doing the RCU stress testing. All with a ton of
other debug options enabled too (ie lockdep etc).

And the result seems to just time out.

I'm inclined to say that this is just "too much testing". Together
with the "it's been going on for a while", I'm going to just ignore
it.

                Linus