public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: Re: [PATCH 1/1] io_uring: fix locked_free_list caches_free()
Date: Tue, 23 Feb 2021 21:56:59 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <3375ffb5767effcf8792e8425e189e78eb843431.1614117221.git.asml.silence@gmail.com>

On 23/02/2021 21:53, Pavel Begunkov wrote:
> Don't forget to zero locked_free_nr, it's not a disaster but makes it
> attempting to flush it with extra locking when there is nothing in the
> list. Also, don't traverse a potentially long list freeing requests
> under spinlock, splice the list and do it afterwards.

Err, it gone totally wrong, will resend

> 
> Signed-off-by: Pavel Begunkov <[email protected]>
> ---
>  fs/io_uring.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index bf9ad810c621..dedcf971e2d5 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -8710,12 +8710,13 @@ static void io_req_caches_free(struct io_ring_ctx *ctx, struct task_struct *tsk)
>  		submit_state->free_reqs = 0;
>  	}
>  
> -	io_req_cache_free(&submit_state->comp.free_list, NULL);
> -
>  	spin_lock_irq(&ctx->completion_lock);
> -	io_req_cache_free(&submit_state->comp.locked_free_list, NULL);
> +	list_splice_init(&cs->locked_free_list, &cs->free_list);
> +	cs->locked_free_nr = 0;
>  	spin_unlock_irq(&ctx->completion_lock);
>  
> +	io_req_cache_free(&submit_state->comp.free_list, NULL);
> +
>  	mutex_unlock(&ctx->uring_lock);
>  }
>  
> 

-- 
Pavel Begunkov

      reply	other threads:[~2021-02-23 22:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 21:53 [PATCH 1/1] io_uring: fix locked_free_list caches_free() Pavel Begunkov
2021-02-23 21:56 ` 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] \
    /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