commit | fcc8abc8d4fcdbddc383091449f3696b411aa8fb | [log] [tgz] |
---|---|---|
author | David Teigland <teigland@redhat.com> | Thu Aug 10 13:31:23 2006 -0500 |
committer | Steven Whitehouse <swhiteho@redhat.com> | Fri Aug 11 09:44:00 2006 -0400 |
tree | 281f7d7af595153904ed3458329f3c868f4e092d | |
parent | 8872187780f6104216c67e7b60c11f708b513c38 [diff] |
[DLM] move kmap to after spin_unlock Doing the kmap() while holding the spinlock was causing recursive spinlock problems. It seems the kmap was scheduling, although there was no warning as I'd expect. Patrick, do we need locking around the kmap? Signed-off-by: David Teigland <teigland@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>