From: Pavel Begunkov <asml.silence@gmail.com>
To: Hao Xu <haoxu@linux.alibaba.com>, Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, Joseph Qi <joseph.qi@linux.alibaba.com>
Subject: Re: [PATCH 1/2] io_uring: fix tw list mess-up by adding tw while it's already in tw list
Date: Wed, 15 Sep 2021 10:44:24 +0100 [thread overview]
Message-ID: <6b9d818b-468e-e409-8dc1-9d4bd586635e@gmail.com> (raw)
In-Reply-To: <20210912162345.51651-2-haoxu@linux.alibaba.com>
On 9/12/21 5:23 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.
>
> 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.
It may get screwed before we get to "node->next = NULL;",
-> async_wake()
-> io_req_task_work_add()
-> async_wake()
-> io_req_task_work_add()
tctx_task_work()
> Fixes: 7cbf1722d5fc ("io_uring: provide FIFO ordering for task_work")
> Signed-off-by: Hao Xu <haoxu@linux.alibaba.com>
> ---
>
> 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 30d959416eba..c16f6be3d46b 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -1216,13 +1216,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) {
> if (ctx->submit_state.compl_nr)
> io_submit_flush_completions(ctx);
> @@ -2126,6 +2130,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-15 9:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 16:23 [PATCH 0/2] poll fixes Hao Xu
2021-09-12 16:23 ` [PATCH 1/2] io_uring: fix tw list mess-up by adding tw while it's already in tw list Hao Xu
2021-09-15 9:44 ` Pavel Begunkov [this message]
2021-09-15 10:48 ` Hao Xu
2021-09-26 9:48 ` Hao Xu
2021-09-29 11:16 ` Pavel Begunkov
2021-09-12 16:23 ` [PATCH 2/2] io_uring: fix race between poll completion and cancel_hash insertion Hao Xu
2021-09-15 9:50 ` Pavel Begunkov
2021-09-15 10:49 ` Hao Xu
2021-09-15 10:12 ` Pavel Begunkov
2021-09-15 10:50 ` 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 \
--in-reply-to=6b9d818b-468e-e409-8dc1-9d4bd586635e@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=haoxu@linux.alibaba.com \
--cc=io-uring@vger.kernel.org \
--cc=joseph.qi@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).