public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: [email protected], Jens Axboe <[email protected]>
Cc: Beld Zhang <[email protected]>
Subject: Re: [PATCH 5.15] io-wq: max_worker fixes
Date: Tue, 19 Oct 2021 23:54:50 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <11f90e6b49410b7d1a88f5d04fb8d95bb86b8cf3.1634671835.git.asml.silence@gmail.com>

On 10/19/21 20:31, Pavel Begunkov wrote:
> First, fix nr_workers checks against max_workers, with max_worker
> registration, it may pretty easily happen that nr_workers > max_workers.
> 
> Also, synchronise writing to acct->max_worker with wqe->lock. It's not
> an actual problem, but as we don't care about io_wqe_create_worker(),
> it's better than WRITE_ONCE()/READ_ONCE().

Jens, can you add

Reported-by: Beld Zhang <[email protected]>

> 
> Fixes: 2e480058ddc2 ("io-wq: provide a way to limit max number of workers")
> Signed-off-by: Pavel Begunkov <[email protected]>
> ---
>   fs/io-wq.c | 7 +++++--
>   1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/io-wq.c b/fs/io-wq.c
> index 811299ac9684..cdf1719f6be6 100644
> --- a/fs/io-wq.c
> +++ b/fs/io-wq.c
> @@ -253,7 +253,7 @@ static bool io_wqe_create_worker(struct io_wqe *wqe, struct io_wqe_acct *acct)
>   		pr_warn_once("io-wq is not configured for unbound workers");
>   
>   	raw_spin_lock(&wqe->lock);
> -	if (acct->nr_workers == acct->max_workers) {
> +	if (acct->nr_workers >= acct->max_workers) {
>   		raw_spin_unlock(&wqe->lock);
>   		return true;
>   	}
> @@ -1290,15 +1290,18 @@ int io_wq_max_workers(struct io_wq *wq, int *new_count)
>   
>   	rcu_read_lock();
>   	for_each_node(node) {
> +		struct io_wqe *wqe = wq->wqes[node];
>   		struct io_wqe_acct *acct;
>   
> +		raw_spin_lock(&wqe->lock);
>   		for (i = 0; i < IO_WQ_ACCT_NR; i++) {
> -			acct = &wq->wqes[node]->acct[i];
> +			acct = &wqe->acct[i];
>   			prev = max_t(int, acct->max_workers, prev);
>   			if (new_count[i])
>   				acct->max_workers = new_count[i];
>   			new_count[i] = prev;
>   		}
> +		raw_spin_unlock(&wqe->lock);
>   	}
>   	rcu_read_unlock();
>   	return 0;
> 

-- 
Pavel Begunkov

  parent reply	other threads:[~2021-10-19 22:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 19:31 [PATCH 5.15] io-wq: max_worker fixes Pavel Begunkov
2021-10-19 19:41 ` Jens Axboe
2021-10-19 22:54 ` Pavel Begunkov [this message]
2021-10-19 23:09   ` 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 \
    [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