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.6-rc1
Date: Tue, 12 Sep 2023 08:01:35 +0000 [thread overview]
Message-ID: <u4g3jh6dnowouthos3tdex2pflzo3hat55e5dc4j6pul3a3uov@y2axtbiura2q> (raw)
Hi all,
I ran the latest blktests (git hash: e0bb3dc05bc7) with v6.6-rc1 kernel. I
observed a couple of new test case failures which are listed below.
Comparing with the failures observed with v6.5 kernel [1], the failure at
zbd/010 is no longer observed (#4 in [1]).
[1] https://lore.kernel.org/linux-block/dycg2iltyeezp6y7bqfhfke6bb3dantkk5nsyk6qjfg2o55esu@liixlkhgtqy3/
List of new failures
====================
#1: nvme/048
#2: nbd/002
Failure description
===================
#1: nvme/048 (rdma and tcp transport)
The test case fails with "BUG: KASAN: slab-use-after-free". Yi Zhang observed
it with linux-next kernel and reported [2]. A fix patch has been provided [3].
[2] https://lore.kernel.org/linux-block/CAHj4cs_CK63uoDpGBGZ6DN4OCTpzkR3UaVgK=LX8Owr8ej2ieQ@mail.gmail.com/
[3] https://lore.kernel.org/linux-block/20230908005702.2183908-1-chengming.zhou@linux.dev/
#2: nbd/002
With kernel v6.6-rc1, nbd/002 fails with the messages below. I reported it
to relevant lists [4]. Kernel test robot reported it also [5].
nbd/002 (tests on partition handling for an nbd device) [failed]
runtime 1.620s ... 0.369s
--- tests/nbd/002.out 2023-04-06 10:11:07.923670528 +0900
+++ /home/shin/Blktests/blktests/results/nodev/nbd/002.out.bad 2023-09-11 12:03:30.901246261 +0900
@@ -1,4 +1,3 @@
Running nbd/002
Testing IOCTL path
-Testing the netlink path
-Test complete
+Didn't have partition on ioctl path
[4] https://lore.kernel.org/linux-block/jvlrypdkye74nea4iys2akwfyvskvpw4x3a2zewwxx3qde22rj@jykkoadmb2m5/
[5] https://lore.kernel.org/linux-block/202309121232.767ff8c4-oliver.sang@intel.com/
reply other threads:[~2023-09-12 8:05 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=u4g3jh6dnowouthos3tdex2pflzo3hat55e5dc4j6pul3a3uov@y2axtbiura2q \
--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).