fabrics: fix uninitialized value in _nvmf_discovery()

Valgrind complained about a conditional jump or move depending on
an uninitialized value created by a stack allocation at
_nvmf_discovery():

==16682== Conditional jump or move depends on uninitialised value(s)
==16682==    at 0x4879DA5: _nvmf_discovery (fabrics.c:2198)
==16682==    by 0x487B341: _discovery_config_json (fabrics.c:2424)
==16682==    by 0x487B549: nvmf_discovery_config_json (fabrics.c:2461)
==16682==    by 0x409A70: fabrics_discovery (fabrics.c:569)
==16682==    by 0x446358: handle_plugin (plugin.c:190)
==16682==    by 0x407760: main (nvme.c:11029)
==16682==  Uninitialised value was created by a stack allocation
==16682==    at 0x4879AF2: _nvmf_discovery (fabrics.c:2102)

Fix the same.

Signed-off-by: Martin George <[email protected]>

Author: martin-gpy

libnvme/src/nvme/fabrics.c

@@ -2134,7 +2134,7 @@ static int _nvmf_discovery(struct nvme_global_ctx *ctx,
 		nvme_ctrl_t cl;
 		bool discover = false;
 		bool disconnect;
-		nvme_ctrl_t child;
+		nvme_ctrl_t child = { 0 };
 		int tmo = fctx->cfg->keep_alive_tmo;
 
 		struct fabric_args trcfg = {