diff options
| author | David Teigland <teigland@redhat.com> | 2012-06-25 18:48:05 (GMT) |
|---|---|---|
| committer | David Teigland <teigland@redhat.com> | 2012-07-16 19:24:43 (GMT) |
| commit | 96006ea6d4eea73466e90ef353bf34e507724e77 (patch) | |
| tree | ba6d5498e805d0042fbbe1a8e0326d8c0d16bceb /arch/blackfin | |
| parent | c503a62103c46d56447f56306b52be6f844689ba (diff) | |
| download | linux-96006ea6d4eea73466e90ef353bf34e507724e77.tar.xz | |
dlm: fix missing dir remove
I don't know exactly how, but in some cases, a dir
record is not removed, or a new one is created when
it shouldn't be. The result is that the dir node
lookup returns a master node where the rsb does not
exist. In this case, The master node will repeatedly
return -EBADR for requests, and the lock requests will
be stuck.
Until all possible ways for this to happen can be
eliminated, a simple and effective way to recover from
this situation is for the supposed master node to send
a standard remove message to the dir node when it
receives a request for a resource it has no rsb for.
Signed-off-by: David Teigland <teigland@redhat.com>
Diffstat (limited to 'arch/blackfin')
0 files changed, 0 insertions, 0 deletions