[DLM] res_recover_locks_count not reset when recover_locks is aborted
authorDavid Teigland <teigland@redhat.com>
Thu, 2 Nov 2006 15:49:02 +0000 (09:49 -0600)
committerSteven Whitehouse <swhiteho@redhat.com>
Thu, 30 Nov 2006 15:35:03 +0000 (10:35 -0500)
commit520698096436f7da5b9142e63e3bed5580c5f14e
tree242196abb5c420855308709db8299e141e2381ac
parentfdda387f73947e6ae511ec601f5b3c6fbb582aac
[DLM] res_recover_locks_count not reset when recover_locks is aborted

Red Hat BZ 213684

If a node sends an lkb to the new master (RCOM_LOCK message) during
recovery and recovery is then aborted on both nodes before it gets a
reply, the res_recover_locks_count needs to be reset to 0 so that when the
subsequent recovery comes along and sends the lkb to the new master again
the assertion doesn't trigger that checks that counter is zero.

Signed-off-by: David Teigland <teigland@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
fs/dlm/recover.c