37ac27cec4
Recent changes to devmapper broke the implicit requirement that UdevWait be called after every call to task.setCookie. Failure to do so results in leaks of semaphores in the LVM code, eventually leading to semaphore exhaustion. Previously this was handled by calling UdevWait in a ubiquitous defer function. While there was initially some concern with deferring the UdevWait function would cause some amount of race possibiliy, the fact that we never return the cookie value or any value used to find it, makes that possibility seem unlikely, so lets go back to that method Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Upstream-commit: 23dcfec1404411489e23fb9b76fc7096db139d04 Component: engine