[dm-devel] racing libdevmapper calls

[Christophe Varoqui]

Hello,

The following command :
# dmsetup remove foo;echo "0 10 linear 8:16 63"|dmsetup create foo &
echo "0 20 linear 8:16 63"|dmsetup create foo

will quite easily produce error message like :
"device-mapper ioctl cmd 3 failed: Device or resource busy"

Is it designed behaviour ?
Can't we expect libdevmapper to serialize its ioctls ?

multipath(8), being run in storms by udev, has trouble with this.
Ideas ?

Regards,
cvaroqui