summaryrefslogtreecommitdiffstats
path: root/fs/dlm/lock.c
diff options
context:
space:
mode:
authorDavid Teigland <teigland@redhat.com>2006-07-25 14:05:09 -0500
committerSteven Whitehouse <swhiteho@redhat.com>2006-07-26 08:42:57 -0400
commit81456807a33c2122e2f1f92acfbaaa77b3d06c3c (patch)
tree5b6d5ed0aa171d564e343b1c51105a79757506eb /fs/dlm/lock.c
parent2b4e926aab7c854a536beee6ba8b9a78a9e00316 (diff)
downloadop-kernel-dev-81456807a33c2122e2f1f92acfbaaa77b3d06c3c.zip
op-kernel-dev-81456807a33c2122e2f1f92acfbaaa77b3d06c3c.tar.gz
[DLM] schedule during long loop through locks
The loop through all waiting locks in recover_waiters can potentially be long, so we should schedule explicitly. Signed-off-by: David Teigland <teigland@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'fs/dlm/lock.c')
-rw-r--r--fs/dlm/lock.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/dlm/lock.c b/fs/dlm/lock.c
index eaad28e..7d38f91 100644
--- a/fs/dlm/lock.c
+++ b/fs/dlm/lock.c
@@ -3193,6 +3193,7 @@ void dlm_recover_waiters_pre(struct dlm_ls *ls)
log_error(ls, "invalid lkb wait_type %d",
lkb->lkb_wait_type);
}
+ schedule();
}
mutex_unlock(&ls->ls_waiters_mutex);
}
OpenPOWER on IntegriCloud