public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: David Jeffery <djeffery@redhat.com>, linux-block@vger.kernel.org
Cc: John Pittman <jpittman@redhat.com>, Omar Sandoval <osandov@osandov.com>
Subject: Re: [PATCH] sbitmap: only queue kyber's wait callback if not already active
Date: Tue, 17 Dec 2019 18:14:55 -0700	[thread overview]
Message-ID: <647af756-3a8a-d895-cbf8-ed3583732817@kernel.dk> (raw)
In-Reply-To: <20191217160024.GA23066@redhat>

On 12/17/19 9:00 AM, David Jeffery wrote:
> Under heavy loads where the kyber I/O scheduler hits the token limits for
> its scheduling domains, kyber can become stuck.  When active requests
> complete, kyber may not be woken up leaving the I/O requests in kyber
> stuck.
> 
> This stuck state is due to a race condition with kyber and the sbitmap
> functions it uses to run a callback when enough requests have completed.
> The running of a sbt_wait callback can race with the attempt to insert the
> sbt_wait.  Since sbitmap_del_wait_queue removes the sbt_wait from the list
> first then sets the sbq field to NULL, kyber can see the item as not on a
> list but the call to sbitmap_add_wait_queue will see sbq as non-NULL. This
> results in the sbt_wait being inserted onto the wait list but ws_active
> doesn't get incremented.  So the sbitmap queue does not know there is a
> waiter on a wait list.
> 
> Since sbitmap doesn't think there is a waiter, kyber may never be
> informed that there are domain tokens available and the I/O never advances.
> With the sbt_wait on a wait list, kyber believes it has an active waiter
> so cannot insert a new waiter when reaching the domain's full state.
> 
> This race can be fixed by only adding the sbt_wait to the queue if the
> sbq field is NULL.  If sbq is not NULL, there is already an action active
> which will trigger the re-running of kyber.  Let it run and add the
> sbt_wait to the wait list if still needing to wait.
> 
> Signed-off-by: David Jeffery <djeffery@redhat.com>
> Reported-by: John Pittman <jpittman@redhat.com>
> Tested-by: John Pittman <jpittman@redhat.com>
> ---
> 
> This bug was reliably being triggered on several test systems.  With the
> fix, the tests no longer fail.
> 
>  sbitmap.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/sbitmap.c b/lib/sbitmap.c
> index 33feec8989f1..af88d1346dd7 100644
> --- a/lib/sbitmap.c
> +++ b/lib/sbitmap.c
> @@ -650,8 +650,8 @@ void sbitmap_add_wait_queue(struct sbitmap_queue *sbq,
>  	if (!sbq_wait->sbq) {
>  		sbq_wait->sbq = sbq;
>  		atomic_inc(&sbq->ws_active);
> +		add_wait_queue(&ws->wait, &sbq_wait->wait);
>  	}
> -	add_wait_queue(&ws->wait, &sbq_wait->wait);
>  }
>  EXPORT_SYMBOL_GPL(sbitmap_add_wait_queue);

This looks good to me, waiting for Omar to take a look (CC'ed).

-- 
Jens Axboe


  reply	other threads:[~2019-12-18  1:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17 16:00 [PATCH] sbitmap: only queue kyber's wait callback if not already active David Jeffery
2019-12-18  1:14 ` Jens Axboe [this message]
2019-12-19 21:41 ` Omar Sandoval

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=647af756-3a8a-d895-cbf8-ed3583732817@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=djeffery@redhat.com \
    --cc=jpittman@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@osandov.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