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-next>] [day] [month] [year] [list]
Message-Id: <20251208132520.1667697-1-jiangshanlai@gmail.com>
Date: Mon,  8 Dec 2025 21:25:16 +0800
From: Lai Jiangshan <jiangshanlai@...il.com>
To: linux-kernel@...r.kernel.org
Cc: Tejun Heo <tj@...nel.org>,
	ying chen <yc1082463@...il.com>,
	Lai Jiangshan <jiangshan.ljs@...group.com>
Subject: [PATCH V5 0/3] workqueue: Factor the way to assign rescuer work

From: Lai Jiangshan <jiangshan.ljs@...group.com>

Previously, the rescuer scanned for all matching work items at once and
processed them within a single rescuer thread, which could cause one
blocking work item to stall all others.

Make the rescuer process work items one-by-one instead of slurping all
matches in a single pass using a cursor.

Changed from V4:

  Control the limit and call send_mayday() in rescuer_thread(), which
  makes rescuer_thread() responsible for ensuring the cursor is not left
  behind.

v4: https://lore.kernel.org/lkml/20251125063617.671199-1-jiangshanlai@gmail.com/

Lai Jiangshan (3):
  workqueue: Refactor send_mayday() to take pwq directly
  workqueue: Process rescuer work items one-by-one using a cursor
  workqueue: Process extra works in rescuer on memory pressure

 kernel/workqueue.c | 119 ++++++++++++++++++++++++++++++++++-----------
 1 file changed, 91 insertions(+), 28 deletions(-)

-- 
2.19.1.6.gb485710b


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ