DPDK may use this NULL pointer to access its member, And then got segmentation fault. But we only need it exit or report normal error. To minimize the impact, and to prevent these going on, we add check the error return for creating NULL mempool in spdk_thread_lib_init_ext in spdk_reactors_init. when error returning from spdk_thread_lib_init_ext in spdk_reactors_init. It contains thread_lib_init which reports error for failed mempool. Thus, codes will return and will not cause segmentation fault. Fixes issue #2620. Signed-off-by: yidong0635 <dongx.yi@intel.com> Change-Id: I63369fdaeb231196e8f8daa826eb5b057ed829b8 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/13842 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Michal Berger <michal.berger@intel.com> |
||
---|---|---|
.. | ||
app_rpc.c | ||
app.c | ||
log_rpc.c | ||
Makefile | ||
reactor.c | ||
scheduler_static.c | ||
spdk_event.map |