[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BYAPR04MB49657A481271ADC1F576377B860D0@BYAPR04MB4965.namprd04.prod.outlook.com>
Date: Tue, 6 Oct 2020 23:55:17 +0000
From: Chaitanya Kulkarni <Chaitanya.Kulkarni@....com>
To: Logan Gunthorpe <logang@...tatee.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
Omar Sandoval <osandov@...ndov.com>
CC: Sagi Grimberg <sagi@...mberg.me>,
Stephen Bates <sbates@...thlin.com>
Subject: Re: [PATCH blktests v2 04/11] nvme: Search for specific subsysnqn in
_find_nvme_loop_dev
On 9/30/20 11:54, Logan Gunthorpe wrote:
> This ensures we find the correct nvme loop device if others exist on a
> given system (which is generally not expected on test systems).
>
> Additionally, this will be required in the upcomming test nvme/037 which
> will have controllers racing with ones being destroyed.
>
> Signed-off-by: Logan Gunthorpe <logang@...tatee.com>
If I create a passthru testcase with :-
1. Create nvme-loop based nvme ctrl backed by null_blk say /dev/nvme1
2. Create a nvme-loop based passthru ctrl backed by /dev/nvme1 say nvme2.
With this patch or this series will I be able to write the testcase ?
Powered by blists - more mailing lists