From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Nilay Shroff <nilay@linux.ibm.com>,
"shinichiro.kawasaki@wdc.com" <shinichiro.kawasaki@wdc.com>,
"dwagner@suse.de" <dwagner@suse.de>
Cc: "kbusch@kernel.org" <kbusch@kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>, "hch@lst.de" <hch@lst.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"venkat88@linux.vnet.ibm.com" <venkat88@linux.vnet.ibm.com>,
"sachinp@linux.vnet.ibm.com" <sachinp@linux.vnet.ibm.com>,
"gjoyce@linux.ibm.com" <gjoyce@linux.ibm.com>
Subject: Re: [PATCHv4 blktests] nvme: add test for creating/deleting file-ns
Date: Mon, 24 Jun 2024 03:04:25 +0000 [thread overview]
Message-ID: <f8519486-e613-4074-94e2-957f5ea2c763@nvidia.com> (raw)
In-Reply-To: <20240619172556.2968660-1-nilay@linux.ibm.com>
On 6/19/24 10:25, Nilay Shroff wrote:
> This is regression test for commit be647e2c76b2 (nvme: use srcu for
> iterating namespace list)[1]. It is fixed in commit ff0ffe5b7c3c(nvme:
> fix namespace removal list)[2].
>
> This test uses a regular file backed loop device for creating and then
> deleting an NVMe namespace in a loop.
>
> [1]https://lore.kernel.org/all/2312e6c3-a069-4388-a863-df7e261b9d70@linux.vnet.ibm.com/
> [2]https://lore.kernel.org/all/20240613164246.75205-1-kbusch@meta.com/
>
> Signed-off-by: Nilay Shroff<nilay@linux.ibm.com>
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2024-06-24 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 17:25 [PATCHv4 blktests] nvme: add test for creating/deleting file-ns Nilay Shroff
2024-06-20 6:35 ` Daniel Wagner
2024-06-20 6:40 ` Nilay Shroff
2024-06-20 6:55 ` Daniel Wagner
2024-06-20 8:28 ` Venkat Rao Bagalkote
2024-06-24 3:04 ` Chaitanya Kulkarni [this message]
2024-06-24 7:57 ` Shinichiro Kawasaki
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=f8519486-e613-4074-94e2-957f5ea2c763@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.com \
--cc=venkat88@linux.vnet.ibm.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