[PATCH nvme-cli] nvme: warn about attaching a namespace to unknown controller

[Keith Busch]

On Thu, Jun 20, 2024 at 06:25:45PM +0530, Nilay Shroff wrote:
> Sometime it's possible for a multi-controller NVMe disk to have only
> one of its controller discovered by the kernel. And if this happens
> then it's also possible for a user to create and then attach a namespace
> to a controller which has not been discovered by the kernel. In such a
> case the attached namespace can't be used for IO because there's no path
> to reach such namespace from the kernel.

Isn't that a pretty normal thing to do, though? Like for an sriov
situation, a primary controller attaches namespaces to secondaries, but
not to itself.