+1
−5
+25
−30
+3
−1
Loading
This was partially fixed in commit 1e481d04 ("nvmf: Do not allow NN to change while connections present"), but we did not handle the case where the user asked to add a NS with a NSID outside the current NN. This patch reworks the logic (again) to be more straightforward and hopefully more obviously correct. Some confusion between max_allowed_nsid and max_nsid is also clarified; if max_allowed_nsid is set, then max_nsid == max_allowed_nsid at all times, so we don't need the extra logic when calculating NN in spdk_nvmf_ctrlr_identify_ctrlr(). Change-Id: If531baf1114e03441ff3e1e1be098071702d9056 Signed-off-by:Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/414894 Tested-by:
SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by:
Changpeng Liu <changpeng.liu@intel.com> Reviewed-by:
Ben Walker <benjamin.walker@intel.com>