]> pilppa.com Git - linux-2.6-omap-h63xx.git/commit
[DLM] Don't delete misc device if lockspace removal fails
authorPatrick Caulfield <pcaulfie@redhat.com>
Wed, 21 Mar 2007 09:23:53 +0000 (09:23 +0000)
committerSteven Whitehouse <swhiteho@redhat.com>
Tue, 1 May 2007 08:10:44 +0000 (09:10 +0100)
commit254da030dfb1b13d42d07e4292a4790d88c6874f
tree8c8f34d6b33232f8081fff6842930d55b2b41140
parent420d2a1028b906f24e836e37089a6ad55ab1848f
[DLM] Don't delete misc device if lockspace removal fails

Currently if the lockspace removal fails the misc device associated with a
lockspace is left deleted. After that there is no way to access the orphaned
lockspace from userland.

This patch recreates the misc device if th dlm_release_lockspace fails. I
believe this is better than attempting to remove the lockspace first because
that leaves an unattached device lying around. The potential gap in which there
is no access to the lockspace between removing the misc device and recreating it
is acceptable ... after all the application is trying to remove it, and only new
users of the lockspace will be affected.

Signed-Off-By: Patrick Caulfield <pcaulfie@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
fs/dlm/user.c