summaryrefslogtreecommitdiffstats
path: root/fs/dlm/requestqueue.c
diff options
context:
space:
mode:
authorDavid Teigland <teigland@redhat.com>2006-11-02 16:45:56 +0100
committerSteven Whitehouse <swhiteho@redhat.com>2006-11-30 16:35:06 +0100
commit435618b75b82b5ee511cc01fcdda9c44adb2f4bd (patch)
treed837e977d881458b2c71a2d1dec5d533ad82fefe /fs/dlm/requestqueue.c
parent[DLM] res_recover_locks_count not reset when recover_locks is aborted (diff)
downloadlinux-435618b75b82b5ee511cc01fcdda9c44adb2f4bd.tar.xz
linux-435618b75b82b5ee511cc01fcdda9c44adb2f4bd.zip
[DLM] status messages ping-pong between unmounted nodes
Red Hat BZ 213682 If two nodes leave the lockspace (while unmounting the fs in the case of gfs) after one has sent a STATUS message to the other, STATUS/STATUS_REPLY messages will then ping-pong between the nodes when neither of them can find the lockspace in question any longer. We kill this by not sending another STATUS message when we get a STATUS_REPLY for an unknown lockspace. Signed-off-by: David Teigland <teigland@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'fs/dlm/requestqueue.c')
0 files changed, 0 insertions, 0 deletions