From: Nilay Shroff <nilay@linux.ibm.com>
To: linux-nvme@lists.infradead.org
Cc: shinichiro.kawasaki@wdc.com, chaitanyak@nvidia.com, hch@lst.de,
kbusch@kernel.org, sagi@grimberg.me, axboe@kernel.dk,
gjoyce@linux.ibm.com
Subject: [PATCHv2 blktests 0/2] add nvme test for creating sleep while atomic kernel BUG
Date: Wed, 4 Dec 2024 17:17:46 +0530 [thread overview]
Message-ID: <20241204114755.190660-1-nilay@linux.ibm.com> (raw)
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").
For fixing regression, as suggested by Christoph[2], I would send a separate
patch upstream.
[1] https://lore.kernel.org/linux-nvme/tqcy3sveity7p56v7ywp7ssyviwcb3w4623cnxj3knoobfcanq@yxgt2mjkbkam/
[2] https://lore.kernel.org/linux-nvme/20241022070252.GA11389@lst.de/
Changes from v1:
- Update the second patch in the series so that we can trigger the
regression 100% of time when we run the test (Chaitanya Kulkarni)
Nilay Shroff (2):
nvme/052: move nvmf_wait_for_ns() to common/nvme
nvme: add test for writing to file-ns just after disabling it
common/nvme | 26 ++++++++++
tests/nvme/052 | 30 +-----------
tests/nvme/055 | 117 +++++++++++++++++++++++++++++++++++++++++++++
tests/nvme/055.out | 2 +
4 files changed, 147 insertions(+), 28 deletions(-)
create mode 100755 tests/nvme/055
create mode 100644 tests/nvme/055.out
--
2.45.2
next reply other threads:[~2024-12-04 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 11:47 Nilay Shroff [this message]
2024-12-04 11:47 ` [PATCHv2 blktests 1/2] nvme/052: move nvmf_wait_for_ns() to common/nvme Nilay Shroff
2024-12-04 11:47 ` [PATCHv2 blktests 2/2] nvme: add test for writing to file-ns just after disabling it Nilay Shroff
2024-12-05 7:32 ` Chaitanya Kulkarni
2024-12-05 9:40 ` Nilay Shroff
2024-12-05 10:47 ` Daniel Wagner
2024-12-05 11:06 ` Nilay Shroff
2024-12-05 11:20 ` Daniel Wagner
2024-12-06 1:49 ` Shinichiro Kawasaki
2024-12-06 1:53 ` Shinichiro Kawasaki
2024-12-06 10:54 ` 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=20241204114755.190660-1-nilay@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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