[PATCH 1/3] nvmet: expose discovery subsystem in sysfs

John Meneghini jmeneghi at redhat.com
Wed Mar 23 10:52:13 PDT 2022


On 3/23/22 13:23, Christoph Hellwig wrote:
> On Wed, Mar 23, 2022 at 01:17:32PM -0400, John Meneghini wrote:
>>
>> Hopefully, with some kind of a design like this, both legacy (non-authenticating)
>> and new (authenticating) hosts and discovery controllers can interoperate.
> 
> This makes much more sense.  But why would a host that is part of a PSK
> setup even use the well known discovery controller at all? Whatever > mechanism is used to share the key should also distribute the actual
> discovery controller to be used and avoid that entire step.

I agree. But that's not what FMDS is doing. They are basically trying to re-invent
the wheel by adding all kinds of arguably redundant mechanisms to the spec. I think
this is what happens when you let a bunch of storage engineers design a network. Just
read TP-8010 and TP-8009 to see what I mean.

I proposed TP-8014 because I saw the mess coming and I wanted some simple way to make
things work... at least with authentication.

/John




More information about the Linux-nvme mailing list