If the socks parameter(passed in uring_sock_group_impl_poll) is NULL, we do not need to handle the sock_flush and prep the pollin task, otherwise it will cause the assert issue when we reap the task when we handle the nvmf_shutdown_tc3 issue. Because in uring_sock_group_impl_remove_sock, we finally set sock->group = NULL. Without this patch, when we call uring_sock_group_impl_poll in this function, pollin_task or write_task are prepared, then in the next round, we will reap those tasks again. PS: Error info can be found in https://ci.spdk.io/results/autotest-per-patch/builds/19186/archive/nvmf-tcp-vg-autotest/build.log Signed-off-by: Ziye Yang <ziye.yang@intel.com> Change-Id: I7e6deaa05e958b52e71e0bbf0ccdd20e35583685 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3031 Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> |
||
---|---|---|
.. | ||
accel | ||
bdev | ||
blob | ||
blobfs | ||
env_dpdk | ||
event | ||
sock | ||
Makefile |