Vivek Goyal 75da15eccc devmapper: Call UdevWait() even in failure path ...

Currently we set up a cookie and upon failure not call UdevWait(). This
does not cleanup the cookie and associated semaphore and system will
soon max out on total number of semaphores.

To avoid this, call UdevWait() even in failure path which in turn will
cleanup associated semaphore.

Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Vincent Batts <vbatts@redhat.com>
Upstream-commit: edc6df256d21eb1d1aa36b241dcc6d4b83d58d75
Component: engine

2014-11-15 09:41:27 -05:00

..

attach_loopback.go

devicemapper: split out devicemapper bindings

2014-11-05 18:10:38 -05:00

devmapper_log.go

devicemapper: split out devicemapper bindings

2014-11-05 18:10:38 -05:00

devmapper_wrapper.go

devicemapper: split out devicemapper bindings

2014-11-05 18:10:38 -05:00

devmapper.go

devmapper: Call UdevWait() even in failure path

2014-11-15 09:41:27 -05:00

ioctl.go

devicemapper: split out devicemapper bindings

2014-11-05 18:10:38 -05:00

MAINTAINERS

pkg/devicemapper: missed MAINTAINERS on split

2014-11-14 11:12:23 -05:00