From: Christoph Hellwig <hch@infradead.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: Yi Zhang <yi.zhang@redhat.com>,
linux-block <linux-block@vger.kernel.org>,
"open list:NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [bug report] WARNING: CPU: 3 PID: 522 at block/genhd.c:144 bdev_count_inflight_rw+0x26e/0x410
Date: Mon, 9 Jun 2025 22:31:03 -0700 [thread overview]
Message-ID: <aEfDF6rxPlT9ie1L@infradead.org> (raw)
In-Reply-To: <dc30d40d-5724-9b54-e3a8-eb66980ddd9e@huaweicloud.com>
On Tue, Jun 10, 2025 at 10:02:19AM +0800, Yu Kuai wrote:
> Looks like this problem is related to nvme mpath, and it's using
> bio based disk IO accounting. I'm not familiar with this driver,
> however, can you try the following bpftrace script to check if
> start request and end request are balanced? From the log I guess
> it's related to mpath error handler, probably requeuing I/O.
nvme-mpath is a bio based driver. It is a bit special in that
it passed down the bio it recived through to the lower-level
request based nvme transport driver, while most remapping drivers
always clone a bio. I suspect that is messing up I/O accounting
here somehow.
next prev parent reply other threads:[~2025-06-10 5:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 3:31 [bug report] WARNING: CPU: 3 PID: 522 at block/genhd.c:144 bdev_count_inflight_rw+0x26e/0x410 Yi Zhang
2025-06-09 9:14 ` Breno Leitao
2025-06-09 14:22 ` Jens Axboe
2025-06-09 16:16 ` Breno Leitao
2025-06-10 2:07 ` Yu Kuai
2025-06-10 16:05 ` Breno Leitao
2025-06-20 4:10 ` Calvin Owens
2025-06-20 6:47 ` Yu Kuai
2025-06-25 1:43 ` Calvin Owens
2025-06-26 7:38 ` Yu Kuai
2025-06-26 4:41 ` Yi Zhang
2025-06-26 7:42 ` Yu Kuai
2025-06-26 8:25 ` Yu Kuai
2025-06-10 2:02 ` Yu Kuai
2025-06-10 5:31 ` Christoph Hellwig [this message]
2025-06-11 0:05 ` Yi Zhang
2025-06-11 6:18 ` Yu Kuai
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=aEfDF6rxPlT9ie1L@infradead.org \
--to=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=yi.zhang@redhat.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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