7ea8a5aae5
Previously, if a reconnect timer was registered when a reset request came, the reset request failed with -EBUSY. However, this means the reset request was queued for a long time until the reconnect timer was expired. When a reconnect timer is registered, reset is not actually in progress. Hence, a new reset request can cancel the reconnect timer and can start reconnection safely. Add a unit test case to verify this change. Signed-off-by: Shuhei Matsumoto <smatsumoto@nvidia.com> Change-Id: Ied8dd0ad822d2fd6829d88cd56cb36bd4fad13f9 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16823 Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com> |
||
|---|---|---|
| .. | ||
| accel | ||
| bdev | ||
| blob | ||
| blobfs | ||
| env_dpdk | ||
| event | ||
| scheduler | ||
| sock | ||
| vfu_device | ||
| Makefile | ||