+78
−4
Loading
This patch attempts to solve naming conflict between CUSE devices created by different SPDK instances. Each NVMe device is enumerated by SPDK process from 0 up to 127. When process attempts to start cuse device tries to set exclusive lock on temporary file "/tmp/spdk_nvme_cuse_lock_<index>" and keep it until device will be stopped. If setting lock fails, index is incremented. It prevents to use the same controller index from few SPDK instances. Change-Id: If744ac23f813bd992efb80ae2b61a1acefb5054c Signed-off-by:Tomasz Kulasek <tomaszx.kulasek@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/474829 Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by:
Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by:
Jim Harris <james.r.harris@intel.com> Reviewed-by:
Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>