From: Sasha Levin <sashal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: stable@vger.kernel.org, asml.silence@gmail.com,
vrazdan@openai.com, krisman@suse.de, io-uring@vger.kernel.org,
gregkh@linuxfoundation.org,
Vishnu Razdan via B4 Relay
<devnull+vrazdan.openai.com@kernel.org>
Subject: Re: [PATCH 6.6.y] io_uring/io-wq: fix worker accounting when canceling creation callbacks
Date: Fri, 28 Aug 2026 10:54:49 -0400 [thread overview]
Message-ID: <apGhOS6PQwdz1JW7@laps> (raw)
In-Reply-To: <ea042ae2-f3bf-4f3b-bfaa-9a7676a9b043@kernel.dk>
On Thu, Aug 27, 2026 at 08:02:34PM -0600, Jens Axboe wrote:
>On 8/27/26 7:46 PM, Sasha Levin wrote:
>>> Decrement nr_workers only when the canceled callback is not
>>> create_worker_cb(). Continuation callbacks still release their reserved
>>> slot, and both callback types retain the existing running-count,
>>> reference-count, and create-state cleanup.
>>>
>>> [ Backport: retain the existing wq->lock protecting worker accounting. ]
>>
>> Queued for 6.6, thanks.
>>
>> I also used this patch for 6.12.
>
>Thanks for doing this - and I'm assuming the AUTOSEL stuff is both
>adapting patches so they apply, and pulling in prerequisites? If
Exactly! It can also do minor adaptations to the prereqs as needed (think cases
like tree-wide changes).
>so, I love it, imho this is exactly what it should be doing. Helps
>maintainers out a lot.
Thanks for the feedback!
--
Thanks,
Sasha
prev parent reply other threads:[~2026-08-28 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026082423-fineness-promotion-9ac5@gregkh>
2026-08-25 16:52 ` [PATCH 6.6.y] io_uring/io-wq: fix worker accounting when canceling creation callbacks Vishnu Razdan via B4 Relay
2026-08-25 16:52 ` Vishnu Razdan
2026-08-28 1:46 ` Sasha Levin
2026-08-28 2:02 ` Jens Axboe
2026-08-28 14:54 ` Sasha Levin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=apGhOS6PQwdz1JW7@laps \
--to=sashal@kernel.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=devnull+vrazdan.openai.com@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@vger.kernel.org \
--cc=krisman@suse.de \
--cc=stable@vger.kernel.org \
--cc=vrazdan@openai.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.