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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 10 Sep 2017 09:36:53 +0200
From:   Markus Trippelsdorf <markus@...ppelsdorf.de>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Tejun Heo <tj@...nel.org>, linux-kernel@...r.kernel.org
Subject: Worker threads in D state since c5a94a618e7ac86 (workqueue: Use
 TASK_IDLE)

Since:

 commit c5a94a618e7ac86b20f53d947f68d7cee6a4c6bc
 Author: Peter Zijlstra <peterz@...radead.org>
 Date:   Wed Aug 23 13:58:44 2017 +0200

     workqueue: Use TASK_IDLE


all worker threads are in D state. They all show up when using "magic
SysRq w". In htop they all have big fat red 'D' in the state column.
Is this really desirable?

I have attached the output of "ps aux" after boot and the SysRq-w
output.

-- 
Markus

View attachment "ps_aux" of type "text/plain" (13591 bytes)

View attachment "SysRq_w" of type "text/plain" (25516 bytes)

Powered by blists - more mailing lists