Daniel Verkamp eb387189c2 nvmf: don't change NN while ctrlrs exist ... This was partially fixed in commit 1e481d0438 ("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>		2018-06-13 21:52:38 +00:00
..
aer.sh	nvmf: don't change NN while ctrlrs exist	2018-06-13 21:52:38 +00:00
bdevperf.sh	test: move the bdev directory up one level	2018-03-23 19:45:09 -04:00
fio.sh	lvol: add destroy_lvol_bdev RPC method	2018-04-24 21:33:56 +00:00
identify_kernel_nvmf.sh	test/nvmf: identify NVM subsystem in kernel test	2018-04-06 18:30:58 -04:00
identify.sh	autotest_common.sh: move to test/common	2018-02-27 20:37:27 -05:00
perf.sh	autotest_common.sh: move to test/common	2018-02-27 20:37:27 -05:00