bdev_nvme: change discovery_poller check to assert
spdk_nvme_probe_poll_async() can only return 0 or -EAGAIN. But the code currently indicates that other values might be possible - so change the code to remove that confusion. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I8e7b2e1183f6650043dd751d610d434d626efa7e Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15110 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
This commit is contained in:
parent
7e17de3d81
commit
6202973033
@ -5307,11 +5307,10 @@ discovery_poller(void *arg)
|
||||
assert(ctx->initializing);
|
||||
stop_discovery(ctx, NULL, ctx->cb_ctx);
|
||||
} else {
|
||||
assert(rc == 0);
|
||||
DISCOVERY_INFOLOG(ctx, "discovery ctrlr connected\n");
|
||||
ctx->rc = rc;
|
||||
if (rc == 0) {
|
||||
get_discovery_log_page(ctx);
|
||||
}
|
||||
get_discovery_log_page(ctx);
|
||||
}
|
||||
}
|
||||
} else {
|
||||
|
Loading…
Reference in New Issue
Block a user