From: Shinichiro 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>
Subject: blktests failures with v6.4-rc2
Date: Thu, 18 May 2023 01:30:13 +0000 [thread overview]
Message-ID: <7i5r76osy6aqb3w3nzpx2x5h2dqoajar6dqipjx6sok4jccjs5@zt5sf6itan36> (raw)
Hi all,
In the blktests discussion at LSF 2023, it was suggested to share test results
with rc1 kernel releases. At this moment, v6.4-rc2 was already released, so here
I report the results of v6.4-rc2 instead of v6.4-rc1.
In short, the result is almost same as that with v6.3 [1]. One new issue was
observed with nvme/033 and nvme/034 with nvme_trtype=rdma condition, but a fix
is already available [2].
Here I share the list of failures with v6.3 and v6.4-rc2 again. As for the
failure #3, fix discussion has started [3] (Thanks!). Please refer [1] for the
detail of the failures.
List of failures
================
#1: block/011
#2: block/024
#3: nvme/003 (fabrics transport)
#4: nvme/030 or nvme/031 (rdma transport with siw)
#5: nvme/* (fc transport)
[1] https://lore.kernel.org/linux-block/rsmmxrchy6voi5qhl4irss5sprna3f5owkqtvybxglcv2pnylm@xmrnpfu3tfpe/
[2] https://lore.kernel.org/linux-rdma/20230510035056.881196-1-guoqing.jiang@linux.dev/
[3] https://lore.kernel.org/linux-nvme/20230511150321.103172-1-bvanassche@acm.org/
reply other threads:[~2023-05-18 1:30 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=7i5r76osy6aqb3w3nzpx2x5h2dqoajar6dqipjx6sok4jccjs5@zt5sf6itan36 \
--to=shinichiro.kawasaki@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).