We use device-mapper to enumerate all dm devices, and filter out
the list of multipath devices by checking the target_type string
name. The code however cancels all scanning if we encounter
target_type=NULL
I don't know how to reproduce that situation, but a user was hitting
it in their setup, and inspecting the lvm2/device-mapper code shows
many places where !target_type is explicitly ignored and processing
continues on to the next device. So I think we should do the same
https://bugzilla.redhat.com/show_bug.cgi?id=1069317
---
src/storage/storage_backend_mpath.c | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/src/storage/storage_backend_mpath.c b/src/storage/storage_backend_mpath.c
index b5b4bb6..bf1b1ab 100644
--- a/src/storage/storage_backend_mpath.c
+++ b/src/storage/storage_backend_mpath.c
@@ -114,12 +114,7 @@ virStorageBackendIsMultipath(const char *dev_name)
dm_get_next_target(dmt, next, &start, &length, &target_type,
¶ms);
- if (target_type == NULL) {
- ret = -1;
- goto out;
- }
-
- if (STREQ(target_type, "multipath"))
+ if (STREQ_NULLABLE(target_type, "multipath"))
ret = 1;
out:
--
2.7.3