From: Guixin Liu <kanie@linux.alibaba.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbusch@kernel.org, axboe@kernel.dk, sagi@grimberg.me,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2] nvme: check at least one ns identification reported
Date: Wed, 6 Nov 2024 18:47:43 +0800 [thread overview]
Message-ID: <dd51a183-6313-454e-afeb-c00f0cb02f30@linux.alibaba.com> (raw)
In-Reply-To: <20241104131529.GA14373@lst.de>
在 2024/11/4 21:15, Christoph Hellwig 写道:
> On Mon, Nov 04, 2024 at 11:14:18AM +0800, Guixin Liu wrote:
>> Per the NVMe spec after 1.3:
>> At least one Namespace Identification Descriptor identifying the
>> namespace (i.e., NIDT field set to 1h, 2h, or 3h).
>> Check there is at least one reported.
> What problem does this try to solve?
I assume that the dm-multipath will not recognize nvme device if nothing
to return,
I was wrong, ignore this path plz.
Best Regards,
Guixin Liu
next prev parent reply other threads:[~2024-11-06 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 3:14 [PATCH v2] nvme: check at least one ns identification reported Guixin Liu
2024-11-04 13:15 ` Christoph Hellwig
2024-11-06 10:47 ` Guixin Liu [this message]
2024-11-07 5:28 ` Christoph Hellwig
2024-11-07 6:18 ` Guixin Liu
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=dd51a183-6313-454e-afeb-c00f0cb02f30@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=axboe@kernel.dk \
--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