archive mirror
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <>
To: "" <>,
	"" <>,
	"" <>
Subject: blktests failures with v6.8-rc1 kernel
Date: Thu, 25 Jan 2024 06:34:40 +0000	[thread overview]
Message-ID: <44i4y3fyqcz6k2pmum6toqylc2lvveb7x37ngskzfof52hoi2r@vxdxdnmggbj5> (raw)

Hi all,

I ran the latest blktests (git hash: 4f6b3fc593bf) with the v6.8-rc1 kernel.
I observed three failures below, which are known for months.

Compared with the v6.7 kernel [1], there is no new failure. Also, the failure of
nvme/003 is no longer observed :) Thank you for the fix.


List of failures
#1: block/011
#2: nvme/* (fc transport)
#3: 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. A RFC fix patch was
   posted recently [3]. It still needs more discussion to be fixed.


#2: nvme/* (fc transport)

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

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

   Test process hang is observed occasionally. Reported to the relevant mailing
   lists in Aug/2023 [4]. Blktests was modified to change the default driver
   from rdma_rxe to siw to avoid impacts on blktests users. The root cause is
   not yet understood.


                 reply	other threads:[~2024-01-25  6:34 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:

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

  git send-email \
    --in-reply-to=44i4y3fyqcz6k2pmum6toqylc2lvveb7x37ngskzfof52hoi2r@vxdxdnmggbj5 \ \ \ \ \

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