linux-kernel - Re: [PATCH] workqueue: add workqueue.mayday_initial

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: <CAJhGHyApLt6AAHUPrYuKUeKiX9de59fou=aPYL5B2QcEmACjAA@mail.gmail.com>
Date: Thu, 13 Nov 2025 23:50:02 +0800
From: Lai Jiangshan <jiangshanlai@...il.com>
To: Tejun Heo <tj@...nel.org>
Cc: ying chen <yc1082463@...il.com>, corbet@....net, linux-doc@...r.kernel.org, 
	linux-kernel@...r.kernel.org, laoar.shao@...il.com
Subject: Re: [PATCH] workqueue: add workqueue.mayday_initial_timeout

Hello.

On Thu, Nov 13, 2025 at 12:03 AM Tejun Heo <tj@...nel.org> wrote:

>
>
> Ah, I see what you mean. The slurping is to avoid potentially O(N^2)
> scanning but that probably the wrong trade-off to make here. I think the
> right solution is making it break out after finding the first matching work
> item and loop outside so that it processes work item one by one.
>

I'm implementing it. A positional dummy work item is added to mark the
position for the next scan after processing the previous one.

I’ll send it soon.

Still, I suggest that the workqueue user eliminate any dependencies among
the work items when using a rescuer. If the memory pressure is not relieved
and no normal workers come to help, it simply won’t work.

thanks
Lai