From: Hao Xu <[email protected]>
To: Pavel Begunkov <[email protected]>,
Jens Axboe <[email protected]>,
[email protected]
Subject: Re: [PATCH 2/3] io_uring: fix io_rsrc_ref_quiesce races
Date: Sat, 20 Feb 2021 14:31:54 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <1b71f4059f088b035ec72307321f051a7be2d44f.1613767375.git.asml.silence@gmail.com>
在 2021/2/20 上午4:45, Pavel Begunkov 写道:
> There are different types of races in io_rsrc_ref_quiesce() between
> ->release() of percpu_refs and reinit_completion(), fix them by always
> resurrecting between iterations. BTW, clean the function up, because
> DRY.
>
> Fixes: 0ce4a72632317 ("io_uring: don't hold uring_lock when calling io_run_task_work*")
> Signed-off-by: Pavel Begunkov <[email protected]>
> ---
> fs/io_uring.c | 46 +++++++++++++---------------------------------
> 1 file changed, 13 insertions(+), 33 deletions(-)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 50d4dba08f82..38ed52065a29 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -7316,19 +7316,6 @@ static void io_sqe_rsrc_set_node(struct io_ring_ctx *ctx,
> percpu_ref_get(&rsrc_data->refs);
> }
>
> -static int io_sqe_rsrc_add_node(struct io_ring_ctx *ctx, struct fixed_rsrc_data *data)
> -{
> - struct fixed_rsrc_ref_node *backup_node;
> -
> - backup_node = alloc_fixed_rsrc_ref_node(ctx);
> - if (!backup_node)
> - return -ENOMEM;
> - init_fixed_file_ref_node(ctx, backup_node);
> - io_sqe_rsrc_set_node(ctx, data, backup_node);
> -
> - return 0;
> -}
> -
> static void io_sqe_rsrc_kill_node(struct io_ring_ctx *ctx, struct fixed_rsrc_data *data)
> {
> struct fixed_rsrc_ref_node *ref_node = NULL;
> @@ -7347,36 +7334,29 @@ static int io_rsrc_ref_quiesce(struct fixed_rsrc_data *data,
> {
> int ret;
>
> - io_sqe_rsrc_kill_node(ctx, data);
> - percpu_ref_kill(&data->refs);
> -
> - /* wait for all refs nodes to complete */
> - flush_delayed_work(&ctx->rsrc_put_work);
> do {
> + io_sqe_rsrc_kill_node(ctx, data);
> + percpu_ref_kill(&data->refs);
> + flush_delayed_work(&ctx->rsrc_put_work);
> +
> ret = wait_for_completion_interruptible(&data->done);
> if (!ret)
> break;
>
> - ret = io_sqe_rsrc_add_node(ctx, data);
> - if (ret < 0)
> - break;
> - /*
> - * There is small possibility that data->done is already completed
> - * So reinit it here
> - */
> + percpu_ref_resurrect(&data->refs);
I've thought about this, if we resurrect data->refs, then we can't
avoid parallel files unregister by percpu_refs_is_dying.
> + io_sqe_rsrc_set_node(ctx, data, backup_node);
> reinit_completion(&data->done);
> mutex_unlock(&ctx->uring_lock);
> ret = io_run_task_work_sig();
> mutex_lock(&ctx->uring_lock);
> - io_sqe_rsrc_kill_node(ctx, data);
> - } while (ret >= 0);
>
> - if (ret < 0) {
> - percpu_ref_resurrect(&data->refs);
> - reinit_completion(&data->done);
> - io_sqe_rsrc_set_node(ctx, data, backup_node);
> - return ret;
> - }
> + if (ret < 0)
> + return ret;
> + backup_node = alloc_fixed_rsrc_ref_node(ctx);
> + if (!backup_node)
> + return -ENOMEM;
Should we resurrect data->refs and reinit completion before
signal or error return?
> + init_fixed_file_ref_node(ctx, backup_node);
> + } while (1);
>
> destroy_fixed_rsrc_ref_node(backup_node);
> return 0;
>
next prev parent reply other threads:[~2021-02-20 6:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 20:45 [PATCH 0/3] rsrc quiesce fixes/hardening Pavel Begunkov
2021-02-19 20:45 ` [PATCH 1/3] io_uring: zero ref_node after killing it Pavel Begunkov
2021-02-19 20:45 ` [PATCH 2/3] io_uring: fix io_rsrc_ref_quiesce races Pavel Begunkov
2021-02-20 6:31 ` Hao Xu [this message]
2021-02-20 14:07 ` Pavel Begunkov
2021-02-20 14:33 ` Pavel Begunkov
2021-02-21 9:46 ` Hao Xu
2021-02-19 20:45 ` [PATCH 3/3] io_uring: keep generic rsrc infra generic Pavel Begunkov
2021-02-19 20:49 ` [PATCH 0/3] rsrc quiesce fixes/hardening Pavel Begunkov
2021-02-20 6:32 ` Hao Xu
2021-02-20 14:14 ` Pavel Begunkov
2021-02-20 0:28 ` Jens Axboe
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=e5c131a0-402d-31df-b5f9-156434bf3f29@linux.alibaba.com \
[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