From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org"
<linux-nvme@lists.infradead.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
nbd@other.debian.org, linux-rdma@vger.kernel.org
Subject: blktests failures with v7.3 kernel
Date: Wed, 21 Oct 2026 12:28:42 +0900 [thread overview]
Message-ID: <atgwg4i6C1zGi1HU@shinmob> (raw)
Hi all,
I ran the latest blktests (git hash: 9ad5a10fa8ed) with the v7.3 kernel. I
observed 2 new failures listed below, which were triggered by kernel changes in
v7.3-rcX. The failures reported for v7.3-rc1 kernel [1] were no longer observed.
[1] https://lore.kernel.org/linux-block/apkYN8Os5A6VXqS6@shinhome/
List of failures
================
#1: nvme/004,031 (rdma transport)
#2: nvme/052
Failure description
===================
#1: nvme/004,031 (rdma transport)
The test cases nvme/004 and nvme/031 fail occasionally for rdma transport
due to the lockdep WARN related to the two locks nvmet_config_sem and
&id_priv->handler_mutex. It is easier to recreate with rxe driver. It is
rather rare, but the failure is observed with siw driver also.
The trigger commit was
2a8513091d2f ("nvme-rdma: parallelize I/O queue allocation and startup")
in v7.3-rc1. I poseted a fix patch candidate [2].
[2] https://lore.kernel.org/linux-nvme/20260922124447.588057-1-shinichiro.kawasaki@opensource.wdc.com/
#2: nvme/052
When it is repeated several times, the test case nvme/052 fails [3]. The
trigger commit was
42b0f5196dc2 ("nvmet: defer setting ns->enabled to false in nvmet_ns_disable()")
in v7.3-rc6. Nilay kindly provided a fix patch [4].
[3] https://lore.kernel.org/all/ar30Q5H1fuyFtDwM@shinmob/
[4] https://lore.kernel.org/linux-nvme/20261002070249.338225-1-nilay@linux.ibm.com/
reply other threads:[~2026-10-21 3:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=atgwg4i6C1zGi1HU@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nbd@other.debian.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