From: Ming Lei <ming.lei@redhat.com>
To: Tian Lan <tilan7663@gmail.com>
Cc: lkp@intel.com, axboe@kernel.dk, linux-block@vger.kernel.org,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
tian.lan@twosigma.com, ming.lei@redhat.com
Subject: Re: [PATCH 1/1] blk-mq: fix blk_mq_hw_ctx active request accounting
Date: Sun, 14 May 2023 22:15:13 +0800 [thread overview]
Message-ID: <ZGDs8U6naf46s+bx@ovpn-8-17.pek2.redhat.com> (raw)
In-Reply-To: <ZGDPLEtUiDeIrCyl@ovpn-8-17.pek2.redhat.com>
On Sun, May 14, 2023 at 08:08:12PM +0800, Ming Lei wrote:
> Hello Tian,
>
> On Sat, May 13, 2023 at 03:05:34PM -0400, Tian Lan wrote:
> > From: Tian Lan <tian.lan@twosigma.com>
> >
> > The nr_active counter continues to increase over time which causes the
> > blk_mq_get_tag to hang until the thread is rescheduled to a different
> > core despite there are still tags available.
> >
> > kernel-stack
> >
> > INFO: task inboundIOReacto:3014879 blocked for more than 2 seconds
> > Not tainted 6.1.15-amd64 #1 Debian 6.1.15~debian11
> > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > task:inboundIOReacto state:D stack:0 pid:3014879 ppid:4557 flags:0x00000000
> > Call Trace:
> > <TASK>
> > __schedule+0x351/0xa20
> > scheduler+0x5d/0xe0
> > io_schedule+0x42/0x70
> > blk_mq_get_tag+0x11a/0x2a0
> > ? dequeue_task_stop+0x70/0x70
> > __blk_mq_alloc_requests+0x191/0x2e0
> >
> > kprobe output showing RQF_MQ_INFLIGHT bit is not cleared before
> > __blk_mq_free_request being called.
>
> RQF_MQ_INFLIGHT won't be cleared when the request is freed normally
> from blk_mq_free_request().
>
> >
> > 320 320 kworker/29:1H __blk_mq_free_request rq_flags 0x220c0 in-flight 1
>
> RQF_MQ_INFLIGHT/RQF_DONTPREP/RQF_IO_STAT/RQF_STATS is set, and it isn't
> a FLUSH request.
>
> > b'__blk_mq_free_request+0x1 [kernel]'
> > b'bt_iter+0x50 [kernel]'
> > b'blk_mq_queue_tag_busy_iter+0x318 [kernel]'
> > b'blk_mq_timeout_work+0x7c [kernel]'
> > b'process_one_work+0x1c4 [kernel]'
> > b'worker_thread+0x4d [kernel]'
> > b'kthread+0xe6 [kernel]'
> > b'ret_from_fork+0x1f [kernel]'
>
> If __blk_mq_free_request() is called from timeout, that means this
> request has been freed by blk_mq_free_request() already, so __blk_mq_dec_active_requests
> should have been run.
>
> However, one case is that __blk_mq_dec_active_requests isn't called in
> blk_mq_end_request_batch, so maybe your driver is nvme with multiple
> NSs, so can you try the following patch?
>
> diff --git a/block/blk-mq.c b/block/blk-mq.c
> index f6dad0886a2f..9c5dd5aa289c 100644
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -1062,6 +1062,9 @@ void blk_mq_end_request_batch(struct io_comp_batch *iob)
> if (iob->need_ts)
> __blk_mq_end_request_acct(rq, now);
>
> + if (rq->rq_flags & RQF_MQ_INFLIGHT)
> + __blk_mq_dec_active_requests(rq->mq_hctx);
> +
> rq_qos_done(rq->q, rq);
The above is actually not correct, given __blk_mq_sub_active_requests()
is done as batch in blk_mq_flush_tag_batch().
So the problem is in the difference between blk_mq_free_request() and
blk_mq_end_request_batch(), wrt. when to call
__blk_mq_dec_active_requests().
So your V2 looks correct, given now both two paths decrease active
requests after req_ref_put_and_test() is done.
And the issue should start from f794f3351f26 ("block: add support for
blk_mq_end_request_batch()").
Thanks,
Ming
next prev parent reply other threads:[~2023-05-14 14:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 14:12 [PATCH 1/1] blk-mq: fix blk_mq_hw_ctx active request accounting Tian Lan
2023-05-13 16:41 ` kernel test robot
2023-05-13 16:41 ` kernel test robot
2023-05-13 19:05 ` Tian Lan
2023-05-13 20:54 ` Simon Horman
2023-05-13 21:15 ` Jens Axboe
2023-05-13 22:11 ` Tian Lan
2023-05-14 1:39 ` Jens Axboe
2023-05-15 12:28 ` Tian Lan
2023-05-13 22:12 ` Tian Lan
2023-05-14 1:52 ` Jens Axboe
2023-05-14 12:20 ` Ming Lei
2023-06-03 22:39 ` [PATCH] " Tian Lan
2023-06-04 0:47 ` Ming Lei
2023-06-03 22:39 ` [PATCH 1/1] " Tian Lan
2023-05-14 14:22 ` Ming Lei
2023-05-14 14:28 ` Tian Lan
2023-05-14 14:53 ` [PATCH] " Tian Lan
2023-05-15 5:54 ` Hannes Reinecke
2023-05-15 12:26 ` Tian Lan
2023-05-25 2:12 ` Ming Lei
2023-06-03 23:20 ` [PATCH 1/1] " Jens Axboe
2023-05-14 12:08 ` Ming Lei
2023-05-14 14:12 ` Tian Lan
2023-05-14 14:15 ` Ming Lei [this message]
2023-05-13 19:11 ` Tian Lan
2023-05-13 16:52 ` 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=ZGDs8U6naf46s+bx@ovpn-8-17.pek2.redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tian.lan@twosigma.com \
--cc=tilan7663@gmail.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