From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Nilay Shroff <nilay@linux.ibm.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
hch <hch@lst.de>, "kbusch@kernel.org" <kbusch@kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"gjoyce@linux.ibm.com" <gjoyce@linux.ibm.com>
Subject: Re: [PATCH blktests 0/2] add nvme test for creating sleep while atomic kernel BUG
Date: Tue, 3 Dec 2024 04:20:22 +0000 [thread overview]
Message-ID: <3a9e7942-68af-477a-a9b4-65fc6df86979@nvidia.com> (raw)
In-Reply-To: <kuvftnq5cjwtzh557umohu7afvndg3tl4lx6qfjjuwd675phk3@y5iaypkzdsz6>
On 11/30/24 01:10, Shinichiro Kawasaki wrote:
> On Nov 29, 2024 / 13:31, Nilay Shroff wrote:
>> Hi,
>>
>> There're two patches in this series. The first patch is a preparation patch
>> for reusing a common function nvmf_wait_for_ns from multiple nvme test scripts.
>> The second patch adds a new nvme regression[1] test for commit 505363957fad
>> ("nvmet: fix nvme status code when namespace is disabled").
> Hi Nilay, thank your very much for the fix actions. Much appreciated.
>
> I tried these blktests patches with the kernel just before the commit
> 505363957fad, at the git hash 6825bdde4434. I expected the new test case fails,
> but it passes. I increased the number of iterations from 10 to 100, but it still
> passes. Do you observe the test case failure on your test systems?
testcase seems really useful to me, but we need to tune it in a such way
it will
have consistent result yet finding the bug in absence of the fix.
-ck
next prev parent reply other threads:[~2024-12-03 4:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 8:01 [PATCH blktests 0/2] add nvme test for creating sleep while atomic kernel BUG Nilay Shroff
2024-11-29 8:01 ` [PATCH blktests 1/2] nvme/052: move nvmf_wait_for_ns() to common/nvme Nilay Shroff
2024-12-03 4:18 ` Chaitanya Kulkarni
2024-11-29 8:01 ` [PATCH blktests 2/2] nvme: add test for writing to file-ns just after disabling it Nilay Shroff
2024-11-30 9:10 ` [PATCH blktests 0/2] add nvme test for creating sleep while atomic kernel BUG Shinichiro Kawasaki
2024-12-03 4:20 ` Chaitanya Kulkarni [this message]
2024-12-03 5:38 ` Nilay Shroff
2024-12-03 8:26 ` Shinichiro Kawasaki
2024-12-03 9:05 ` Nilay Shroff
2024-12-06 1:09 ` Shinichiro Kawasaki
2024-12-03 8:26 ` Chaitanya Kulkarni
2024-12-04 10:08 ` Nilay Shroff
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=3a9e7942-68af-477a-a9b4-65fc6df86979@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=sagi@grimberg.me \
--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