public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>,
	[email protected], [email protected]
Subject: Re: [PATCH 1/1] io_uring: fix overflowed reqs cancellation
Date: Wed, 27 May 2020 20:18:23 +0300	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <7acb1a15ee5a79103d71372d6330b19c5397a482.1590574948.git.asml.silence@gmail.com>

On 27/05/2020 13:23, Pavel Begunkov wrote:
> Overflowed requests in io_uring_cancel_files() should be shed only of
> inflight and overflowed refs. All other left references are owned by
> someone else. E.g. a submission ref owned by __io_queue_sqe() but not
> yet reached the point of releasing it.
> 
> However, if an overflowed request in io_uring_cancel_files() had extra
> refs, after refcount_sub_and_test(2) check fails, it
> 
> - tries to cancel the req, which is already going away. That's pointless,
> just go for the next lap of inflight waiting.
> 
> - io_put_req() underflowing req->refs of a potentially freed request.e
Probably needs v2, please disregard this for now.

> 
> Fixes: 2ca10259b418 ("io_uring: prune request from overflow list on flush")
> Signed-off-by: Pavel Begunkov <[email protected]>
> ---
>  fs/io_uring.c | 16 +++++-----------
>  1 file changed, 5 insertions(+), 11 deletions(-)
> 
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index de6547e68626..01851a74bb12 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -7483,19 +7483,13 @@ static void io_uring_cancel_files(struct io_ring_ctx *ctx,
>  			WRITE_ONCE(ctx->rings->cq_overflow,
>  				atomic_inc_return(&ctx->cached_cq_overflow));
>  
> -			/*
> -			 * Put inflight ref and overflow ref. If that's
> -			 * all we had, then we're done with this request.
> -			 */
> -			if (refcount_sub_and_test(2, &cancel_req->refs)) {
> -				io_free_req(cancel_req);
> -				finish_wait(&ctx->inflight_wait, &wait);
> -				continue;
> -			}
> +			/* Put inflight ref and overflow ref. */
> +			io_double_put_req(cancel_req);
> +		} else {
> +			io_wq_cancel_work(ctx->io_wq, &cancel_req->work);
> +			io_put_req(cancel_req);
>  		}
>  
> -		io_wq_cancel_work(ctx->io_wq, &cancel_req->work);
> -		io_put_req(cancel_req);
>  		schedule();
>  		finish_wait(&ctx->inflight_wait, &wait);
>  	}
> 

-- 
Pavel Begunkov

      reply	other threads:[~2020-05-27 17:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 10:23 [PATCH 1/1] io_uring: fix overflowed reqs cancellation Pavel Begunkov
2020-05-27 17:18 ` Pavel Begunkov [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 \
    [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