Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: UtUNBcDvoX/Zpg5m4HuyXQ/cYrs/kLE5WswRjgYNNFkrT8xgMTz30Pa+Df5q7BgKehAiDd+j51
 EJe/o4Gac+6hrvtr/VPpvHsvukkRDdJ98i+VhEBa8pTMI48TzXSaHgPyte/NJRYcT8r5u4Y1Xp
 f7RnaPWYakfdOAU9F+WDrcmcmBTJE7rKoODHC5/6PRELi2molg6RZSB9SeQQLyWPkEYBiCDnaR
 Rm/vd9diOS0BtPoUL4vOYqmLoLJuYRPGto4yA4w9KJ7+y8wy4q0XSs8MawLPcaPWnjjGd4mfwX
 pKs=
From:   Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To:     Logan Gunthorpe <logang@deltatee.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
        "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
        Omar Sandoval <osandov@osandov.com>
CC:     Sagi Grimberg <sagi@grimberg.me>,
        Stephen Bates <sbates@raithlin.com>
Subject: Re: [PATCH blktests v2 04/11] nvme: Search for specific subsysnqn in
 _find_nvme_loop_dev
Thread-Topic: [PATCH blktests v2 04/11] nvme: Search for specific subsysnqn in
 _find_nvme_loop_dev
Thread-Index: AQHWl1ssGO8rVJrUsk6VJGLZV4glGg==
Date:   Tue, 6 Oct 2020 23:55:17 +0000
Message-ID: <BYAPR04MB49657A481271ADC1F576377B860D0@BYAPR04MB4965.namprd04.prod.outlook.com>
References: <20200930185422.11494-1-logang@deltatee.com>
 <20200930185422.11494-5-logang@deltatee.com>
Accept-Language: en-US
Content-Language: en-US
wdcipoutbound: EOP-TRUE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b718a2b5-51f5-4217-c671-08d86a5346f7
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Oct 2020 23:55:17.7238
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b61c8803-16f3-4c35-9b17-6f65f441df86
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: DztorwYjmsHmM7c5HvF3ktwDjJFO91QCYvnKM1PmrW2MhIPN+QQXqXnrvpS+GzNrwz/VHfGpP6q3GJEM+WXRxiC5tRI/LmhLww72xEEgy98=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR04MB6898
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 9/30/20 11:54, Logan Gunthorpe wrote:=0A=
> This ensures we find the correct nvme loop device if others exist on a=0A=
> given system (which is generally not expected on test systems).=0A=
>=0A=
> Additionally, this will be required in the upcomming test nvme/037 which=
=0A=
> will have controllers racing with ones being destroyed.=0A=
>=0A=
> Signed-off-by: Logan Gunthorpe <logang@deltatee.com>=0A=
=0A=
If I create a passthru testcase with :-=0A=
=0A=
1. Create nvme-loop based nvme ctrl backed by null_blk say /dev/nvme1=0A=
=0A=
2. Create a nvme-loop based passthru ctrl backed by /dev/nvme1 say nvme2.=
=0A=
=0A=
=0A=
With this patch or this series will I be able to write the testcase ?=0A=
=0A=