archive mirror
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <>
To: "" <>,
	"" <>,
	"" <>
Subject: blktests failures with v6.6
Date: Wed, 1 Nov 2023 04:09:38 +0000	[thread overview]
Message-ID: <6qycihftrxsdvuvpsvmkbe2swy5u2isrtu6jiyf3khzusdzilc@34kda7iutwdq> (raw)

Hi all,

I ran the latest blktests (git hash: 3f75e6241f6b) with v6.6 kernel, and obseved
four failures below. They are all known for months.

As for the two other failures observed with v6.6-rc1 kernel [1], they are no
longer observed with v6.6 kernel. Good.


List of failures
#1: block/011
#2: nvme/003 (fabrics transport)
#3: nvme/* (fc transport)
#4: srp/002, 011 (rdma_rxe driver)

Failure description

#1: block/011

   The test case fails with NVME devices due to lockdep WARNING "possible
   circular locking dependency detected". Reported in Sep/2022 [2]. In LSF
   2023, it was noted that this failure should be fixed.

   Also, it was found recently that this test case still causes failure of
   following tests. Fix work is ongoing [3].


#2: nvme/003 (fabrics transport)

   When nvme test group is run with trtype=rdma or tcp, the test case fails
   due to lockdep WARNING "possible circular locking dependency detected".
   Reported in May/2023. Fix discussions were held [4][5].


#3: nvme/* (fc transport)

   With trtype=fc configuration, test run on nvme test group hangs. Daniel is
   driving fix work.

#4: srp/002, 011 (rdma_rxe driver)

   Test process hang is observed occasionally. Reported to the relevant mailing
   lists in Aug/2023 [6]. Blktests was modified to change default driver from
   rdma_rxe to siw to avoid impacts on blktests users. Root cause is not yet
   understood. Bob and Bart have spent time to chase it down (Thank you).


             reply	other threads:[~2023-11-01  4:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01  4:09 Shinichiro Kawasaki [this message]
2023-11-01 10:33 ` blktests failures with v6.6 Hannes Reinecke
2023-11-01 12:37   ` Shinichiro Kawasaki

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6qycihftrxsdvuvpsvmkbe2swy5u2isrtu6jiyf3khzusdzilc@34kda7iutwdq \ \ \ \ \

* 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).