Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	Keith Busch <kbusch@kernel.org>
Cc: "hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>,
	"axboe@fb.com" <axboe@fb.com>,
	"gjoyce@linux.ibm.com" <gjoyce@linux.ibm.com>,
	Chaitanya Kulkarni <chaitanyak@nvidia.com>
Subject: Re: [PATCHv2] nvmet-passthru: clear EUID/NGUID/UUID while using loop target
Date: Tue, 1 Oct 2024 19:37:45 +0530	[thread overview]
Message-ID: <ab01d3a4-3f23-4c77-9fe7-c59b25041d44@linux.ibm.com> (raw)
In-Reply-To: <89d4d73d-daef-441d-beae-e9ba52001911@nvidia.com>

Hi Keith,

A gentle ping about this patch. Does this now look good to you? 

Thanks,
--Nilay

On 9/24/24 09:04, Chaitanya Kulkarni wrote:
> On 9/21/2024 12:05 AM, Nilay Shroff wrote:
>> When nvme passthru is configured using loop target, the clear_ids
>> attribute is, by default, set to true. This attribute would ensure that
>> EUID/NGUID/UUID is cleared for the loop passthru target.
>>
>> The newer NVMe disk supporting the NVMe spec 1.3 or higher, typically,
>> implements the support for "Namespace Identification Descriptor list"
>> command. This command when issued from host returns EUID/NGUID/UUID
>> assigned to the inquired namespace. Not clearing these values, while
>> using nvme passthru using loop target, would result in NVMe host driver
>> rejecting the namespace. This check was implemented in the commit
>> 2079f41ec6ff ("nvme: check that EUI/GUID/UUID are globally unique").
>>
>> The fix implemented in this commit ensure that when host issues ns-id
>> descriptor list command, the EUID/NGUID/UUID are cleared by passthru
>> target. In fact, the function nvmet_passthru_override_id_descs() which
>> clears those unique ids already exits, so we just need to ensure that
>> ns-id descriptor list command falls through the corretc code path. And
>> while we're at it, we also combines the three passthru admin command
>> cases together which shares the same code.
>>
>> Reviewed-by: Christoph Hellwig <hch@lst.de>
>> Signed-off-by: Nilay Shroff <nilay@linux.ibm.com>
>> ---
> 
> Looks good.
> 
> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
> 
> -ck
> 
> 


  reply	other threads:[~2024-10-01 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-21  7:05 [PATCHv2] nvmet-passthru: clear EUID/NGUID/UUID while using loop target Nilay Shroff
2024-09-24  3:34 ` Chaitanya Kulkarni
2024-10-01 14:07   ` Nilay Shroff [this message]
2024-10-01 20:40     ` Keith Busch
  -- strict thread matches above, loose matches on Subject: below --
2024-09-22 17:28 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=ab01d3a4-3f23-4c77-9fe7-c59b25041d44@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=axboe@fb.com \
    --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 \
    /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