+20
−13
Loading
I think the original intention here was for possible processing of multiple events. But use of STAILQ would actually be unsafe without a lock in that case, since a second event could be inserted while the targeted thread is removing the first event. So just attach the ctx directly to the qpair. Existing code that destroys the qpair while this message is en route can still set that ctx->qpair to NULL to ensure the message is handled safely once received. While here also add a check to catch unexpected case where LAST_WQE_REACHED is received more than once for the same rqpair. Signed-off-by:Jim Harris <jim.harris@samsung.com> Change-Id: I24b76d4b50d7438b8c41a715f6e3e025769fb50c Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/24985 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Reviewed-by:
Aleksey Marchuk <alexeymar@nvidia.com> Reviewed-by:
Shuhei Matsumoto <smatsumoto@nvidia.com> Community-CI: Mellanox Build Bot Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com>