From: Nilay Shroff <nilay@linux.ibm.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>,
"nbd@other.debian.org" <nbd@other.debian.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Yi Zhang <yi.zhang@redhat.com>
Subject: Re: blktests failures with v6.11-rc1 kernel
Date: Fri, 2 Aug 2024 22:19:29 +0530 [thread overview]
Message-ID: <79a7ec0d-c22d-44cf-a832-13da05a1fcbd@linux.ibm.com> (raw)
In-Reply-To: <ljqlgkvhkojsmehqddmeo4dng6l3yaav6le2uslsumfxivluwu@m7lkx3j4mkkw>
On 8/2/24 18:04, Shinichiro Kawasaki wrote:
> CC+: Yi Zhang,
>
> On Aug 02, 2024 / 17:46, Nilay Shroff wrote:
>>
>>
>> On 8/2/24 14:39, Shinichiro Kawasaki wrote:
>>>
>>> #3: nvme/052 (CKI failure)
>>>
>>> The CKI project reported that nvme/052 fails occasionally [4].
>>> This needs further debug effort.
>>>
>>> nvme/052 (tr=loop) (Test file-ns creation/deletion under one subsystem) [failed]
>>> runtime ... 22.209s
>>> --- tests/nvme/052.out 2024-07-30 18:38:29.041716566 -0400
>>> +++ /mnt/tests/gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/archive/production/kernel-tests-production.zip/storage/blktests/nvme/nvme-loop/blktests/results/nodev_tr_loop/nvme/052.out.bad 2024-07-30 18:45:35.438067452 -0400
>>> @@ -1,2 +1,4 @@
>>> Running nvme/052
>>> +cat: /sys/block/nvme1n2/uuid: No such file or directory
>>> +cat: /sys/block/nvme1n2/uuid: No such file or directory
>>> Test complete
>>>
>>> [4] https://datawarehouse.cki-project.org/kcidb/tests/13669275
>>
>> I just checked the console logs of the nvme/052 and from the logs it's
>> apparent that all namespaces were created successfully and so it's strange
>> to see that the test couldn't access "/sys/block/nvme1n2/uuid".
>
> I agree that it's strange. I think the "No such file or directory" error
> happened in _find_nvme_ns(), and it checks existence of the uuid file before
> the cat command. I have no idea why the error happens.
>
Yes exactly, and these two operations (checking the existence of uuid
and cat command) are not atomic. So the only plausible theory I have at this
time is "if namespace is deleted after checking the existence of uuid but
before cat command is executed" then this issue may potentially manifests.
Furthermore, as you mentioned, this issue is seen on the test machine
occasionally, so I asked if there's a possibility of simultaneous blktest
or some other tests running on this system.
Thanks,
--Nilay
next prev parent reply other threads:[~2024-08-02 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 9:09 blktests failures with v6.11-rc1 kernel Shinichiro Kawasaki
2024-08-02 12:16 ` Nilay Shroff
2024-08-02 12:34 ` Shinichiro Kawasaki
2024-08-02 16:49 ` Nilay Shroff [this message]
2024-08-13 7:06 ` Yi Zhang
2024-08-14 12:35 ` Nilay Shroff
2024-08-19 12:34 ` Shinichiro Kawasaki
2024-08-19 13:35 ` Nilay Shroff
2024-08-20 1:50 ` Yi Zhang
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=79a7ec0d-c22d-44cf-a832-13da05a1fcbd@linux.ibm.com \
--to=nilay@linux.ibm.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 \
--cc=yi.zhang@redhat.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