diff options
| author | Patrick Caulfield <pcaulfie@redhat.com> | 2007-03-21 09:23:53 +0000 |
|---|---|---|
| committer | Steven Whitehouse <swhiteho@redhat.com> | 2007-05-01 09:10:44 +0100 |
| commit | 254da030dfb1b13d42d07e4292a4790d88c6874f (patch) | |
| tree | 8c8f34d6b33232f8081fff6842930d55b2b41140 /ipc | |
| parent | 420d2a1028b906f24e836e37089a6ad55ab1848f (diff) | |
| download | op-kernel-dev-254da030dfb1b13d42d07e4292a4790d88c6874f.zip op-kernel-dev-254da030dfb1b13d42d07e4292a4790d88c6874f.tar.gz | |
[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>
Diffstat (limited to 'ipc')
0 files changed, 0 insertions, 0 deletions
