linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	"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>
Subject: Re: blktests failures with v6.6
Date: Wed, 1 Nov 2023 11:33:08 +0100	[thread overview]
Message-ID: <d1d179ea-ae0f-497a-a2af-f1c60cf90362@suse.de> (raw)
In-Reply-To: <6qycihftrxsdvuvpsvmkbe2swy5u2isrtu6jiyf3khzusdzilc@34kda7iutwdq>

On 11/1/23 05:09, Shinichiro Kawasaki wrote:
> 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.
> 
> [1] https://lore.kernel.org/linux-block/u4g3jh6dnowouthos3tdex2pflzo3hat55e5dc4j6pul3a3uov@y2axtbiura2q/
> 
> 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] https://lore.kernel.org/linux-block/20220930001943.zdbvolc3gkekfmcv@shindev/
>     [3] https://github.com/kawasaki/blktests/commit/f540cbb0eeb66e2c76a88efbe65a2b59d55630fd
> 
> #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].
> 
>     [4] https://lore.kernel.org/linux-nvme/20230511150321.103172-1-bvanassche@acm.org/
>     [5] https://lore.kernel.org/linux-nvme/5cb63b10-72ab-4b7c-7574-48583ea8ffd1@grimberg.me/
> 
Just send a patchset which should resolve these issues.
Can you test with them?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                Kernel Storage Architect
hare@suse.de                              +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Ivo Totev, Andrew
Myers, Andrew McDonald, Martje Boudien Moerman


  reply	other threads:[~2023-11-01 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01  4:09 blktests failures with v6.6 Shinichiro Kawasaki
2023-11-01 10:33 ` Hannes Reinecke [this message]
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:
  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=d1d179ea-ae0f-497a-a2af-f1c60cf90362@suse.de \
    --to=hare@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.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;
as well as URLs for NNTP newsgroup(s).