public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Hao Xu <haoxu@linux.alibaba.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>,
	Joseph Qi <joseph.qi@linux.alibaba.com>
Subject: Re: [PATCH 1/2] io-wq: fix bug of creating io-wokers unconditionally
Date: Tue, 10 Aug 2021 00:12:35 +0800	[thread overview]
Message-ID: <0760b085-0d10-eea2-eedf-76d4047a7084@linux.alibaba.com> (raw)
In-Reply-To: <2df89a6c-edf4-8b1d-85d2-720ee25d816c@kernel.dk>

在 2021/8/9 下午10:18, Jens Axboe 写道:
> On 8/9/21 8:08 AM, Hao Xu wrote:
>> 在 2021/8/9 下午10:01, Jens Axboe 写道:
>>> On 8/8/21 7:54 AM, Hao Xu wrote:
>>>> The former patch to add check between nr_workers and max_workers has a
>>>> bug, which will cause unconditionally creating io-workers. That's
>>>> because the result of the check doesn't affect the call of
>>>> create_io_worker(), fix it by bringing in a boolean value for it.
>>>>
>>>> Fixes: 21698274da5b ("io-wq: fix lack of acct->nr_workers < acct->max_workers judgement")
>>>> Signed-off-by: Hao Xu <haoxu@linux.alibaba.com>
>>>> ---
>>>>    fs/io-wq.c | 19 ++++++++++++++-----
>>>>    1 file changed, 14 insertions(+), 5 deletions(-)
>>>>
>>>> diff --git a/fs/io-wq.c b/fs/io-wq.c
>>>> index 12fc19353bb0..5536b2a008d1 100644
>>>> --- a/fs/io-wq.c
>>>> +++ b/fs/io-wq.c
>>>> @@ -252,14 +252,15 @@ static void io_wqe_wake_worker(struct io_wqe *wqe, struct io_wqe_acct *acct)
>>>>    
>>>>    		raw_spin_lock_irq(&wqe->lock);
>>>>    		if (acct->nr_workers < acct->max_workers) {
>>>> -			atomic_inc(&acct->nr_running);
>>>> -			atomic_inc(&wqe->wq->worker_refs);
>>>>    			acct->nr_workers++;
>>>>    			do_create = true;
>>>>    		}
>>>>    		raw_spin_unlock_irq(&wqe->lock);
>>>> -		if (do_create)
>>>> +		if (do_create) {
>>>> +			atomic_inc(&acct->nr_running);
>>>> +			atomic_inc(&wqe->wq->worker_refs);
>>>>    			create_io_worker(wqe->wq, wqe, acct->index);
>>>> +		}
>>>>    	}
>>>
>>> I don't get this hunk - we already know we're creating a worker, what's the
>>> point in moving the incs?
>>>
>> Actually not much difference, I think we don't need to protect
>> nr_running and worker_refs by wqe->lock, so narrow the range of
>> raw_spin_lock_irq - raw_spin_unlock_irq
> 
> Agree, we don't need it, but it's not a fix as such. I'd rather defer that
> one to a separate cleanup for the next release.
I'll send it later.
> 


  reply	other threads:[~2021-08-09 16:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-08 13:54 [PATCH 0/2] bug fix for nr_workers Hao Xu
2021-08-08 13:54 ` [PATCH 1/2] io-wq: fix bug of creating io-wokers unconditionally Hao Xu
2021-08-09 14:01   ` Jens Axboe
2021-08-09 14:08     ` Hao Xu
2021-08-09 14:18       ` Jens Axboe
2021-08-09 16:12         ` Hao Xu [this message]
2021-08-08 13:54 ` [PATCH 2/2] io-wq: fix IO_WORKER_F_FIXED issue in create_io_worker() 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=0760b085-0d10-eea2-eedf-76d4047a7084@linux.alibaba.com \
    --to=haoxu@linux.alibaba.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --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