]> pilppa.org Git - linux-2.6-omap-h63xx.git/commit
projects / linux-2.6-omap-h63xx.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8872187) | patch
[DLM] move kmap to after spin_unlock
authorDavid Teigland <teigland@redhat.com>
Thu, 10 Aug 2006 18:31:23 +0000 (13:31 -0500)
committerSteven Whitehouse <swhiteho@redhat.com>
Fri, 11 Aug 2006 13:44:00 +0000 (09:44 -0400)
commitfcc8abc8d4fcdbddc383091449f3696b411aa8fb
tree281f7d7af595153904ed3458329f3c868f4e092dtree | snapshot
parent8872187780f6104216c67e7b60c11f708b513c38commit | 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>
fs/dlm/lowcomms.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.