https://github.com/torvalds/linux
Revision 537632e0a54a5355cdd0330911d18c3b773f9cf7 authored by Boaz Harrosh on 11 July 2012, 12:27:13 UTC, committed by Boaz Harrosh on 20 July 2012, 08:49:25 UTC
The read-4-write pages are locked in address ascending order.
But where unlocked in a way easiest for coding. Fix that,
locks should be released in opposite order of locking, .i.e
descending address order.

I have not hit this dead-lock. It was found by inspecting the
dbug print-outs. I suspect there is an higher lock at caller that
protects us, but fix it regardless.

Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
1 parent 62b62ad
History
Tip revision: 537632e0a54a5355cdd0330911d18c3b773f9cf7 authored by Boaz Harrosh on 11 July 2012, 12:27:13 UTC
ore: Unlock r4w pages in exact reverse order of locking
Tip revision: 537632e
File Mode Size
Documentation
arch
block
crypto
drivers
firmware
fs
include
init
ipc
kernel
lib
mm
net
samples
scripts
security
sound
tools
usr
virt
.gitignore -rw-r--r-- 1014 bytes
.mailmap -rw-r--r-- 4.4 KB
COPYING -rw-r--r-- 18.3 KB
CREDITS -rw-r--r-- 92.7 KB
Kbuild -rw-r--r-- 2.5 KB
Kconfig -rw-r--r-- 252 bytes
MAINTAINERS -rw-r--r-- 208.2 KB
Makefile -rw-r--r-- 46.0 KB
README -rw-r--r-- 17.3 KB
REPORTING-BUGS -rw-r--r-- 3.3 KB

README

back to top