diff options
| author | David Teigland <teigland@redhat.com> | 2006-11-02 15:49:02 (GMT) |
|---|---|---|
| committer | Steven Whitehouse <swhiteho@redhat.com> | 2006-11-30 15:35:03 (GMT) |
| commit | 520698096436f7da5b9142e63e3bed5580c5f14e (patch) | |
| tree | 242196abb5c420855308709db8299e141e2381ac /fs/dlm/util.c | |
| parent | fdda387f73947e6ae511ec601f5b3c6fbb582aac (diff) | |
| download | linux-520698096436f7da5b9142e63e3bed5580c5f14e.tar.xz | |
[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>
Diffstat (limited to 'fs/dlm/util.c')
0 files changed, 0 insertions, 0 deletions