From: Zhu Yanjun <zyjzyj2000@gmail.com>
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>,
"nbd@other.debian.org" <nbd@other.debian.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: blktests failures with v6.10-rc1 kernel
Date: Fri, 31 May 2024 16:35:23 +0200 [thread overview]
Message-ID: <6cd21274-50b3-44c5-af48-179cbd08b1ba@linux.dev> (raw)
In-Reply-To: <wnucs5oboi4flje5yvtea7puvn6zzztcnlrfz3lpzlwgblrxgw@7wvqdzioejgl>
On 31.05.24 03:54, Shinichiro Kawasaki wrote:
> Hi all,
>
> (I added linux-rdma list to the To list since blktests nvme and srp groups
> depend on rdma drivers.)
>
> I ran the latest blktests (git hash: 698f1a024cb4) with the v6.10-rc1 kernel,
> and observed a couple of failures as listed below.
>
> There are two notable differences from the result with kernel v6.9-rc1 [1].
> The first one is srp/002,011 hangs with the rdma rxe driver, which was discussed
IIRC, the problem with srp/002, 011 also occurs with siw driver, do you
make tests with siw driver to verify whether the problem with srp/002,
011 is also fixed or not?
Thanks,
Zhu Yanjun
> at LSF 2024. I no longer observe these hangs with v6.10-rc1 kernel. Great :) I
> found Bob Pearson made a number of improvements in the driver. I guess these
> changes avoided the hangs. Thank you very much!
>
> The other difference is nbd/002 failure. CKI project still reports it for
> v6.10-rc1 kernel [2]. Recently Josef provided blktests side fix [3] (Thanks!),
> and it has not yet applied to the CKI test run set up. The fix was made for
> nbd/001, but I expect that it will avoid the nbd/002 failure also.
>
> [1] https://lore.kernel.org/linux-block/m6a437jvfwzq2jfytvvk62zpgu7e4bjvegr7x73pihhkp5me5c@sh6vs3s7w754/
> [2] https://datawarehouse.cki-project.org/kcidb/tests/12631448
> [3] https://lore.kernel.org/linux-block/9377610cbdc3568c172cd7c5d2e9d36da8dd2cf4.1716312272.git.josef@toxicpanda.com/
>
>
> List of failures
> ================
> #1: nvme/041 (fc transport)
> #2: nvme/050
>
> Failure description
> ===================
>
> #1: nvme/041 (fc transport)
>
> With the trtype=fc configuration, nvme/041 fails:
>
> nvme/041 (Create authenticated connections) [failed]
> runtime 2.677s ... 4.823s
> --- tests/nvme/041.out 2023-11-29 12:57:17.206898664 +0900
> +++ /home/shin/Blktests/blktests/results/nodev/nvme/041.out.bad 2024-03-19 14:50:56.399101323 +0900
> @@ -2,5 +2,5 @@
> Test unauthenticated connection (should fail)
> disconnected 0 controller(s)
> Test authenticated connection
> -disconnected 1 controller(s)
> +disconnected 0 controller(s)
> Test complete
>
> nvme/044 had same failure symptom until the kernel v6.9. A solution was
> suggested and discussed in Feb/2024 [4].
>
> [4] https://lore.kernel.org/linux-nvme/20240221132404.6311-1-dwagner@suse.de/
>
> #2: nvme/050
>
> The test case fails occasionally with a QEMU NVME device. The failure cause
> is the lockdep WARN among ctrl->namespaces_rwsem, dev->shutdown_lock and
> workqueue work completion. After LSF 2024 discussion, Sagi and Keith worked
> on the solution and Keith provided the fix [5]. Thank you!
>
> [5] https://lore.kernel.org/linux-nvme/20240524155345.243814-1-kbusch@meta.com/
next prev parent reply other threads:[~2024-05-31 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 1:54 blktests failures with v6.10-rc1 kernel Shinichiro Kawasaki
2024-05-31 14:35 ` Zhu Yanjun [this message]
2024-05-31 20:01 ` Bart Van Assche
2024-05-31 20:06 ` Zhu Yanjun
2024-05-31 20:08 ` Bart Van Assche
2024-05-31 20:35 ` Zhu Yanjun
2024-05-31 20:46 ` Bart Van Assche
2024-06-01 1:49 ` Zhu Yanjun
2024-06-04 6:57 ` 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=6cd21274-50b3-44c5-af48-179cbd08b1ba@linux.dev \
--to=zyjzyj2000@gmail.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 \
--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