From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "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 v5.19-rc1
Date: Fri, 10 Jun 2022 09:32:20 +0000 [thread overview]
Message-ID: <19d09611-42cc-5a81-d676-c5375865c14c@nvidia.com> (raw)
In-Reply-To: <717734c9-c633-fb48-499e-7e3e15113020@nvidia.com>
Shinichiro,
>
>> #6: nvme/032: Failed at the first run after system reboot.
>> Used QEMU NVME device as TEST_DEV.
>>
ofcourse we need to fix this issue but can you also
try it with the real H/W ?
>> runtime ... 8.458s
>> something found in dmesg:
>> [ 1589.976481] run blktests nvme/032 at 2022-06-09 10:57:20
>>
>> [ 1597.221547] ======================================================
>> [ 1597.221549] WARNING: possible circular locking dependency detected
>> [ 1597.221551] 5.19.0-rc1 #1 Not tainted
>> [ 1597.221554] ------------------------------------------------------
>> [ 1597.221554] check/970 is trying to acquire lock:
>> [ 1597.221556] ffff8881026f8cb8 (kn->active#227){++++}-{0:0}, at: kernfs_remove_by_name_ns+0x90/0xe0
>> [ 1597.221580]
>> but task is already holding lock:
>> ...
>>
-ck
next prev parent reply other threads:[~2022-06-10 9:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 23:53 blktests failures with v5.19-rc1 Shinichiro Kawasaki
2022-06-10 8:07 ` Christoph Hellwig
2022-06-10 9:22 ` Chaitanya Kulkarni
2022-06-10 9:32 ` Chaitanya Kulkarni [this message]
2022-06-10 12:25 ` Shinichiro Kawasaki
2022-06-10 13:15 ` Yi Zhang
2022-06-10 14:47 ` Keith Busch
2022-06-11 8:34 ` Yi Zhang
2022-06-14 1:09 ` Shinichiro Kawasaki
2022-06-14 2:23 ` Keith Busch
2022-06-14 2:38 ` Chaitanya Kulkarni
2022-06-14 4:00 ` Shinichiro Kawasaki
2022-06-15 19:47 ` Bjorn Helgaas
2022-06-15 22:01 ` Chaitanya Kulkarni
2022-06-15 23:13 ` Yi Zhang
2022-06-16 4:42 ` Shinichiro Kawasaki
2022-06-16 17:55 ` Chaitanya Kulkarni
2022-06-15 23:16 ` Keith Busch
2022-07-19 4:50 ` Shinichiro Kawasaki
2022-07-19 22:31 ` Bjorn Helgaas
2022-07-20 2:27 ` Shinichiro Kawasaki
2022-12-19 11:27 ` Shinichiro Kawasaki
2022-12-29 18:13 ` Bjorn Helgaas
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=19d09611-42cc-5a81-d676-c5375865c14c@nvidia.com \
--to=chaitanyak@nvidia.com \
--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