linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org
Cc: brking@linux.vnet.ibm.com, bart.vanassche@wdc.com,
	Jens Axboe <axboe@kernel.dk>
Subject: [PATCH 1/6] blk-mq-tag: check for NULL rq when iterating tags
Date: Fri,  4 Aug 2017 09:04:17 -0600	[thread overview]
Message-ID: <1501859062-11120-2-git-send-email-axboe@kernel.dk> (raw)
In-Reply-To: <1501859062-11120-1-git-send-email-axboe@kernel.dk>

Since we introduced blk-mq-sched, the tags->rqs[] array has been
dynamically assigned. So we need to check for NULL when iterating,
since there's a window of time where the bit is set, but we haven't
dynamically assigned the tags->rqs[] array position yet.

This is perfectly safe, since the memory backing of the request is
never going away while the device is alive.

Signed-off-by: Jens Axboe <axboe@kernel.dk>
---
 block/blk-mq-tag.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/block/blk-mq-tag.c b/block/blk-mq-tag.c
index d0be72ccb091..b856b2827157 100644
--- a/block/blk-mq-tag.c
+++ b/block/blk-mq-tag.c
@@ -214,7 +214,7 @@ static bool bt_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)
 		bitnr += tags->nr_reserved_tags;
 	rq = tags->rqs[bitnr];
 
-	if (rq->q == hctx->queue)
+	if (rq && rq->q == hctx->queue)
 		iter_data->fn(hctx, rq, iter_data->data, reserved);
 	return true;
 }
@@ -249,8 +249,8 @@ static bool bt_tags_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)
 	if (!reserved)
 		bitnr += tags->nr_reserved_tags;
 	rq = tags->rqs[bitnr];
-
-	iter_data->fn(rq, iter_data->data, reserved);
+	if (rq)
+		iter_data->fn(rq, iter_data->data, reserved);
 	return true;
 }
 
-- 
2.7.4

  reply	other threads:[~2017-08-04 15:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 15:04 [PATCHSET v2 0/6] block: more scalable inflight tracking Jens Axboe
2017-08-04 15:04 ` Jens Axboe [this message]
2017-08-04 19:34   ` [PATCH 1/6] blk-mq-tag: check for NULL rq when iterating tags Bart Van Assche
2017-08-04 19:35     ` Jens Axboe
2017-08-08 22:28   ` Omar Sandoval
2017-08-04 15:04 ` [PATCH 2/6] block: pass in queue to inflight accounting Jens Axboe
2017-08-08 22:30   ` Omar Sandoval
2017-08-04 15:04 ` [PATCH 3/6] block: make part_in_flight() take an array of two ints Jens Axboe
2017-08-04 19:38   ` Bart Van Assche
2017-08-04 19:40     ` Jens Axboe
2017-08-08 22:42   ` Omar Sandoval
2017-08-08 23:45     ` Jens Axboe
2017-08-04 15:04 ` [PATCH 4/6] blk-mq: provide internal in-flight variant Jens Axboe
2017-08-04 19:43   ` Bart Van Assche
2017-08-04 19:45     ` Jens Axboe
2017-08-08 22:46   ` Omar Sandoval
2017-08-04 15:04 ` [PATCH 5/6] blk-mq: enable checking two part inflight counts at the same time Jens Axboe
2017-08-04 19:44   ` Bart Van Assche
2017-08-04 19:56     ` Jens Axboe
2017-08-06  0:17       ` Bart Van Assche
2017-08-08 22:48   ` Omar Sandoval
2017-08-08 23:47     ` Jens Axboe
2017-08-09  7:14       ` Omar Sandoval
2017-08-09 14:13         ` Jens Axboe
2017-08-04 15:04 ` [PATCH 6/6] sbitmap: make sb_for_each_fn() return void Jens Axboe
2017-08-04 19:49   ` Bart Van Assche
2017-08-04 19:50     ` 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 \
    --in-reply-to=1501859062-11120-2-git-send-email-axboe@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=bart.vanassche@wdc.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=linux-block@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).