+++ This bug was initially created as a clone of Bug #177934 +++ Description of problem: If you call dlm_release_lockspace() in libdlm from userland from an application A, application B's reference to the open lockspace will become invalid if application B has no locks granted at the time of the release. e.g. Program A Program B Create LS 'Foo' Open LS 'Foo' Acquire lock Release lock Release LS Acquire lock <-- returns -1 / ENOENT ------------------------------------------------------------ The idea here is to provide a workaround in the plugin itself. The simplest solution is to take a null lock in the lockspace so that release_lockspace doesn't have anything to check.
Fixes in CVS - RHEL4/head/STABLE
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0240.html