f7ddfcf743
spdk_reactors_fini() is unconditionally called in spdk_app_fini() at the end of every application and it currently throws a ton of warning messages if the reactors weren't initialized yet [1]. Let's silence those warnings. [1] $ spdk_tgt -c invalid.conf [...] *WARNING*: Called spdk_reactor_get() while the g_reactors array was NULL! *WARNING*: Called spdk_reactor_get() while the g_reactors array was NULL! *WARNING*: Called spdk_reactor_get() while the g_reactors array was NULL! *WARNING*: Called spdk_reactor_get() while the g_reactors array was NULL! *WARNING*: Called spdk_reactor_get() while the g_reactors array was NULL! (Apparently SPDK_ENV_FOREACH_CORE iterates through 128 cores if the dpdk env framework wasn't initialized. SPDK calls spdk_reactor_get() on each core and that's what generates the warnings) Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Change-Id: Ic3a2355ef6d2e0d0e1cc125ba21cc6a802b355bc Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/470736 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> |
||
---|---|---|
.. | ||
app.c | ||
json_config.c | ||
Makefile | ||
reactor.c | ||
rpc.c | ||
subsystem.c |