[PATCH 0/3] nvmet: use right MNAN value for controllers

[Chaitanya Kulkarni]

On 6/13/21 13:03, Chaitanya Kulkarni wrote:
> Hi,
>
> In current implementation we report MNAN value as NVMET_MAX_NAMESPACES.
>
> For Spec regarding MNAN value:-
>
> If the controller supports Asymmetric Namespace Access Reporting, then
> this field shall be set to a _non-zero_ value that is less than or equal
> to the NN value.
>
> The first patch sets identify controller MNAN value to subsys->max_nsid
> that is always less than or equal to the NN.
>
> The second patch prevents creating the controller from subsys if subsys
> has 0 namespaces since it will report 0 (invalid) MNAN value.
>
> The third patch prevents reporting such subsys in the dicovery log page.
>
> -ck


Please ignore this as some of the block tests are failing I need to figure
out whether any of those needs a fix or something is wrong in this series,
sorry for the noise.