linux-kernel - Re: [PATCH v1 0/2] io_uring/io-wq: let workers exit when unused

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

Message-ID: <0b9539f3-d30e-47ba-b577-8b65855a05a0@kernel.dk>
Date: Tue, 3 Feb 2026 07:09:42 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Li Chen <me@...ux.beauty>
Cc: Pavel Begunkov <asml.silence@...il.com>,
 io-uring <io-uring@...r.kernel.org>,
 linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 0/2] io_uring/io-wq: let workers exit when unused

On 2/3/26 12:47 AM, Li Chen wrote:
> Hi Jens,
> 
> > If you still want a test, I'm happy to write it. Since you've already
>  > > tweaked/applied the v1 series, I can send the test as a standalone
>  > > follow-up patch (no v2).
>  > > 
>  > > If kselftest is preferred, I'll base it on the same CRIU-style workload:
>  > > spawn iou-wrk-* via io_uring, quiesce/close the last ring, and check the
>  > > worker exits within a short timeout.
>  > 
>  > That sounds like the right way to do the test. Preferably a liburing
>  > test/ case would be better, we don't do a lot of in-kernel selftests so
>  > far. But liburing has everything.
> 
> Thanks for your suggestion. I just adapted my local test program to
> liburing and posted the liburing PR here:
> https://github.com/axboe/liburing/pull/1529

Thanks, merged!

-- 
Jens Axboe