The Lorax project found a regression in kpartx -d behavior introduced
by the following commit: 9bdfa3eb8e24b668e6c2bb882cddb0ccfe23ed5b
This patch should fix the problem. It's easy to reproduce this problem
(I did it on Fedora 28) with the following commands:
# kpartx -av disk.img
...
# kpartx -dv disk.img
Notice that the loop devices and partition mappings created by the first
command are not cleaned up by the second command.
Stef Walter (1):
kpartx: Use absolute paths to create mappings
kpartx/kpartx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.17.1
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
