[PATCH 0/4] nvmet: fix configfs attr update handling for discovered subsystems

[Max Gurtovoy]

On 25/09/2025 1:13, Keith Busch wrote:
> On Wed, Sep 24, 2025 at 11:26:00PM +0300, Max Gurtovoy wrote:
>> 1. Forbid changes to controller ID min/max attributes values on already
>>     discovered subsystems.
>> 2. Switch cntlid ida allocation from global to per-subsystem scope,
>>     matching the granularity of controller ID ranges.
>> 3. Forbid changes to vendor ID and subsystem vendor ID attributes values
>>     on already discovered subsystems.
>> 4. Forbid changes to max_qid attribute values on already discovered
>>     subsystems.
> Is there a reason these should be changeable after they're initialized
> even prior to being discovered?

I think we can make the subsystem not-changeable during the first 
successful call of nvmet_port_subsys_allow_link() related to the 
specific subsystem.

Then make all the _store() functions to fail after first linkage to some 
nvmet_port.

any thoughts ?