mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-25 07:05:28 +00:00
08c0ea16fc
Rather than returning true/false and having the caller check if the vHBA was actually created, let's do that check within the CreateVport function. That way the caller can faithfully assume success based on a name start the thread looking for the LUNs. Prior to this change it's possible that the vHBA wasn't really created (e.g if the call to virVHBAGetHostByWWN returned NULL), we'd claim success, but in reality there'd be no vHBA for the pool. This also fixes a second yet seen issue that if the nodedev was present, but the parent by name wasn't provided (perhaps parent by wwnn/wwpn or by fabric_name), then a failure would be returned. For this path it shouldn't be an error - we should just be happy that something else is managing the device and we don't have to create/delete it. The end result is that the createVport code can now just start the refresh thread once it gets a non NULL name back. Signed-off-by: John Ferlan <jferlan@redhat.com> |
||
|---|---|---|
| .. | ||
| parthelper.c | ||
| storage_backend_disk.c | ||
| storage_backend_disk.h | ||
| storage_backend_fs.c | ||
| storage_backend_fs.h | ||
| storage_backend_gluster.c | ||
| storage_backend_gluster.h | ||
| storage_backend_iscsi.c | ||
| storage_backend_iscsi.h | ||
| storage_backend_logical.c | ||
| storage_backend_logical.h | ||
| storage_backend_mpath.c | ||
| storage_backend_mpath.h | ||
| storage_backend_rbd.c | ||
| storage_backend_rbd.h | ||
| storage_backend_scsi.c | ||
| storage_backend_scsi.h | ||
| storage_backend_sheepdog_priv.h | ||
| storage_backend_sheepdog.c | ||
| storage_backend_sheepdog.h | ||
| storage_backend_vstorage.c | ||
| storage_backend_vstorage.h | ||
| storage_backend_zfs.c | ||
| storage_backend_zfs.h | ||
| storage_backend.c | ||
| storage_backend.h | ||
| storage_driver.c | ||
| storage_driver.h | ||
| storage_util.c | ||
| storage_util.h | ||