[PATCH 3/3] nvmet: do not allow to create a subsystem with the discovery NQN
Hannes Reinecke
hare at suse.de
Tue Mar 15 01:45:23 PDT 2022
On 3/15/22 09:10, Christoph Hellwig wrote:
> On Mon, Mar 14, 2022 at 11:53:33AM +0100, Hannes Reinecke wrote:
>> configfs will only protect us against duplication of subsystem NQNs,
>> but discovery subsystems might have two NQNs, the standard discovery NQN
>> (which will be used as the configfs directory name), and the additional
>> unique subsystem NQN.
>
> This is something that we should probably pick up as fix ASAP. Can
> you add a proper fixes tag and submit it stand-alone?
Will need to rework the patch, as in its current form it relies on the
discovery subsystem to be exposed in configfs.
But yes, can do.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare at suse.de +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
More information about the Linux-nvme
mailing list