From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>
Cc: io-uring@vger.kernel.org,
Caleb Sander Mateos <csander@purestorage.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] io_uring: move local task_work in exit cancel loop
Date: Wed, 14 Jan 2026 10:18:44 -0700 [thread overview]
Message-ID: <176841112450.443561.17209876764056331154.b4-ty@kernel.dk> (raw)
In-Reply-To: <20260114085405.346872-1-ming.lei@redhat.com>
On Wed, 14 Jan 2026 16:54:05 +0800, Ming Lei wrote:
> With IORING_SETUP_DEFER_TASKRUN, task work is queued to ctx->work_llist
> (local work) rather than the fallback list. During io_ring_exit_work(),
> io_move_task_work_from_local() was called once before the cancel loop,
> moving work from work_llist to fallback_llist.
>
> However, task work can be added to work_llist during the cancel loop
> itself. There are two cases:
>
> [...]
Applied, thanks!
[1/1] io_uring: move local task_work in exit cancel loop
commit: da579f05ef0faada3559e7faddf761c75cdf85e1
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2026-01-14 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 8:54 [PATCH] io_uring: move local task_work in exit cancel loop Ming Lei
2026-01-14 17:18 ` Jens Axboe [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=176841112450.443561.17209876764056331154.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox