From: Pavel Begunkov <[email protected]>
To: Hao Xu <[email protected]>, Jens Axboe <[email protected]>
Cc: [email protected], Joseph Qi <[email protected]>
Subject: Re: [PATCH 2/2] io_uring: fix tw list mess-up by adding tw while it's already in tw list
Date: Wed, 29 Sep 2021 12:13:43 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 9/27/21 1:36 PM, Hao Xu wrote:
> For multishot mode, there may be cases like:
> io_poll_task_func()
> -> add_wait_queue()
> async_wake()
> ->io_req_task_work_add()
> this one mess up the running task_work list
> since req->io_task_work.node is in use.
By the time req->io_task_work.func() is called, node->next is undefined
and free to use. io_req_task_work_add() will override it without looking
at a prior value and that's fine, as the calling code doesn't touch it
after the callback.
> similar situation for req->io_task_work.fallback_node.
> Fix it by set node->next = NULL before we run the tw, so that when we
> add req back to the wait queue in middle of tw running, we can safely
> re-add it to the tw list.
I might be missing what is the problem you're trying to fix. Does the
above makes sense? It doesn't sound like node->next=NULL can solve
anything.
> Fixes: 7cbf1722d5fc ("io_uring: provide FIFO ordering for task_work")
> Signed-off-by: Hao Xu <[email protected]>
> ---
> fs/io_uring.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index d0b358b9b589..f667d6286438 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -1250,13 +1250,17 @@ static void io_fallback_req_func(struct work_struct *work)
> struct io_ring_ctx *ctx = container_of(work, struct io_ring_ctx,
> fallback_work.work);
> struct llist_node *node = llist_del_all(&ctx->fallback_llist);
> - struct io_kiocb *req, *tmp;
> + struct io_kiocb *req;
> bool locked = false;
>
> percpu_ref_get(&ctx->refs);
> - llist_for_each_entry_safe(req, tmp, node, io_task_work.fallback_node)
> + req = llist_entry(node, struct io_kiocb, io_task_work.fallback_node);
> + while (member_address_is_nonnull(req, io_task_work.fallback_node)) {
> + node = req->io_task_work.fallback_node.next;
> + req->io_task_work.fallback_node.next = NULL;
> req->io_task_work.func(req, &locked);
> -
> + req = llist_entry(node, struct io_kiocb, io_task_work.fallback_node);
> + }
> if (locked) {
> io_submit_flush_completions(ctx);
> mutex_unlock(&ctx->uring_lock);
> @@ -2156,6 +2160,7 @@ static void tctx_task_work(struct callback_head *cb)
> locked = mutex_trylock(&ctx->uring_lock);
> percpu_ref_get(&ctx->refs);
> }
> + node->next = NULL;
> req->io_task_work.func(req, &locked);
> node = next;
> } while (node);
>
--
Pavel Begunkov
next prev parent reply other threads:[~2021-09-29 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 12:35 [PATCH 0/2] fixes of poll Hao Xu
2021-09-27 12:35 ` [PATCH 1/2] io_uring: fix concurrent poll interruption Hao Xu
2021-09-27 13:33 ` Hao Xu
2021-09-27 12:36 ` [PATCH 2/2] io_uring: fix tw list mess-up by adding tw while it's already in tw list Hao Xu
2021-09-29 11:13 ` Pavel Begunkov [this message]
2021-09-29 12:08 ` Hao Xu
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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