All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagi@grimberg.me>
To: Jianchao Wang <jianchao.w.wang@oracle.com>, axboe@kernel.dk
Cc: hch@lst.de, jthumshirn@suse.de, hare@suse.de,
	josef@toxicpanda.com, bvanassche@acm.org, keith.busch@intel.com,
	jsmart2021@gmail.com, linux-block@vger.kernel.org,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/8] blk-mq: change the method of iterating busy tags of a request_queue
Date: Wed, 20 Mar 2019 11:52:52 -0700	[thread overview]
Message-ID: <bf563d09-c243-5bf5-ab3e-0fa2bd583edd@grimberg.me> (raw)
In-Reply-To: <1552640264-26101-3-git-send-email-jianchao.w.wang@oracle.com>



On 3/15/19 1:57 AM, Jianchao Wang wrote:
> tags->rqs[] will not been cleaned when free driver tag and there
> is a window between get driver tag and write tags->rqs[], so we
> may see stale rq in tags->rqs[] which may have been freed, as
> following case,
> blk_mq_get_request         blk_mq_queue_tag_busy_iter
>    -> blk_mq_get_tag
>                               -> bt_for_each
>                                 -> bt_iter
>                                   -> rq = taags->rqs[]
>                                   -> rq->q
>    -> blk_mq_rq_ctx_init
>      -> data->hctx->tags->rqs[rq->tag] = rq;
> 
> To fix this, the blk_mq_queue_tag_busy_iter is changed in this
> patch to use tags->static_rqs[] instead of tags->rqs[]. We have
> to identify whether there is a io scheduler attached to decide
> to use hctx->tags or hctx->sched_tags. And we will try to get a
> non-zero q_usage_counter before that, so it is safe to access
> them. Add 'inflight' parameter to determine to iterate in-flight
> requests or just busy tags. A correction here is that
> part_in_flight should count the busy tags instead of rqs that
> have got driver tags.

IMO, instead of this parameter, add a wrapper like
blk_mq_queue_tag_inflight_iter() or keep the parameter out until
we actually have a user that calls it for busy and not inflight.

Other than that, I think that iterating over static_rqs is a good
solution to the problem described.

WARNING: multiple messages have this Message-ID (diff)
From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 2/8] blk-mq: change the method of iterating busy tags of a request_queue
Date: Wed, 20 Mar 2019 11:52:52 -0700	[thread overview]
Message-ID: <bf563d09-c243-5bf5-ab3e-0fa2bd583edd@grimberg.me> (raw)
In-Reply-To: <1552640264-26101-3-git-send-email-jianchao.w.wang@oracle.com>



On 3/15/19 1:57 AM, Jianchao Wang wrote:
> tags->rqs[] will not been cleaned when free driver tag and there
> is a window between get driver tag and write tags->rqs[], so we
> may see stale rq in tags->rqs[] which may have been freed, as
> following case,
> blk_mq_get_request         blk_mq_queue_tag_busy_iter
>    -> blk_mq_get_tag
>                               -> bt_for_each
>                                 -> bt_iter
>                                   -> rq = taags->rqs[]
>                                   -> rq->q
>    -> blk_mq_rq_ctx_init
>      -> data->hctx->tags->rqs[rq->tag] = rq;
> 
> To fix this, the blk_mq_queue_tag_busy_iter is changed in this
> patch to use tags->static_rqs[] instead of tags->rqs[]. We have
> to identify whether there is a io scheduler attached to decide
> to use hctx->tags or hctx->sched_tags. And we will try to get a
> non-zero q_usage_counter before that, so it is safe to access
> them. Add 'inflight' parameter to determine to iterate in-flight
> requests or just busy tags. A correction here is that
> part_in_flight should count the busy tags instead of rqs that
> have got driver tags.

IMO, instead of this parameter, add a wrapper like
blk_mq_queue_tag_inflight_iter() or keep the parameter out until
we actually have a user that calls it for busy and not inflight.

Other than that, I think that iterating over static_rqs is a good
solution to the problem described.

  parent reply	other threads:[~2019-03-20 18:53 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15  8:57 [PATCH 0/8]: blk-mq: use static_rqs to iterate busy tags Jianchao Wang
2019-03-15  8:57 ` Jianchao Wang
2019-03-15  8:57 ` [PATCH 1/8] blk-mq: get rid of the synchronize_rcu in __blk_mq_update_nr_hw_queues Jianchao Wang
2019-03-15  8:57   ` Jianchao Wang
2019-03-17  6:14   ` Ming Lei
2019-03-17  6:14     ` Ming Lei
2019-03-15  8:57 ` [PATCH 2/8] blk-mq: change the method of iterating busy tags of a request_queue Jianchao Wang
2019-03-15  8:57   ` Jianchao Wang
2019-03-15 16:16   ` Keith Busch
2019-03-15 16:16     ` Keith Busch
2019-03-17  6:50     ` Ming Lei
2019-03-17  6:50       ` Ming Lei
2019-03-18 15:53       ` Keith Busch
2019-03-18 15:53         ` Keith Busch
2019-03-18  1:49     ` jianchao.wang
2019-03-18  1:49       ` jianchao.wang
2019-03-20 18:52   ` Sagi Grimberg [this message]
2019-03-20 18:52     ` Sagi Grimberg
2019-03-21  1:33     ` jianchao.wang
2019-03-21  1:33       ` jianchao.wang
2019-03-15  8:57 ` [PATCH 3/8] blk-mq: use blk_mq_queue_tag_busy_iter in debugfs Jianchao Wang
2019-03-15  8:57   ` Jianchao Wang
2019-03-15  8:57 ` [PATCH 4/8] mtip32xx: use blk_mq_queue_tag_busy_iter Jianchao Wang
2019-03-15  8:57   ` Jianchao Wang
2019-03-15  8:57 ` [PATCH 5/8] nbd: " Jianchao Wang
2019-03-15  8:57   ` Jianchao Wang
2019-03-18 17:16   ` Bart Van Assche
2019-03-18 17:16     ` Bart Van Assche
2019-03-19  2:04     ` jianchao.wang
2019-03-19  2:04       ` jianchao.wang
2019-03-15  8:57 ` [PATCH 6/8] skd: " Jianchao Wang
2019-03-15  8:57   ` Jianchao Wang
2019-03-18 17:20   ` Bart Van Assche
2019-03-18 17:20     ` Bart Van Assche
2019-03-19  1:54     ` jianchao.wang
2019-03-19  1:54       ` jianchao.wang
2019-03-15  8:57 ` [PATCH 7/8] nvme: " Jianchao Wang
2019-03-15  8:57   ` Jianchao Wang
2019-03-15 16:33   ` James Smart
2019-03-15 16:33     ` James Smart
2019-03-15 16:39     ` James Smart
2019-03-15 16:39       ` James Smart
2019-03-15 16:49       ` Hannes Reinecke
2019-03-15 16:49         ` Hannes Reinecke
2019-03-18  7:00     ` jianchao.wang
2019-03-18  7:00       ` jianchao.wang
2019-03-15  8:57 ` [PATCH 8/8] blk-mq: remove blk_mq_tagset_busy_iter Jianchao Wang
2019-03-15  8:57   ` Jianchao Wang
2019-03-15  9:20 ` [PATCH 0/8]: blk-mq: use static_rqs to iterate busy tags Christoph Hellwig
2019-03-15  9:20   ` Christoph Hellwig
2019-03-15  9:44   ` jianchao.wang
2019-03-15  9:44     ` jianchao.wang
2019-03-15 16:19     ` Bart Van Assche
2019-03-15 16:19       ` Bart Van Assche
2019-03-18  2:47       ` jianchao.wang
2019-03-18  2:47         ` jianchao.wang
2019-03-15 13:30   ` Josef Bacik
2019-03-15 13:30     ` Josef Bacik
2019-03-18 17:28 ` Bart Van Assche
2019-03-18 17:28   ` Bart Van Assche
2019-03-19  1:25   ` jianchao.wang
2019-03-19  1:25     ` jianchao.wang
2019-03-19 15:10     ` Bart Van Assche
2019-03-19 15:10       ` Bart Van Assche
2019-03-19 15:25       ` Keith Busch
2019-03-19 15:25         ` Keith Busch
2019-03-20 18:38         ` Sagi Grimberg
2019-03-20 18:38           ` Sagi Grimberg

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=bf563d09-c243-5bf5-ab3e-0fa2bd583edd@grimberg.me \
    --to=sagi@grimberg.me \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jianchao.w.wang@oracle.com \
    --cc=josef@toxicpanda.com \
    --cc=jsmart2021@gmail.com \
    --cc=jthumshirn@suse.de \
    --cc=keith.busch@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.