Boaz Harrosh 537632e0a5 ore: Unlock r4w pages in exact reverse order of locking ... 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>		2012-07-20 11:49:25 +03:00
..
BUGS
common.h
dir.c	exofs: remove the second argument of k[un]map_atomic()	2012-03-20 21:48:22 +08:00
exofs.h	exofs: Add SYSFS info for autologin/pNFS export	2012-05-21 12:24:01 +03:00
file.c
inode.c	vfs: Rename end_writeback() to clear_inode()	2012-05-06 13:43:41 +08:00
Kbuild	exofs: Add SYSFS info for autologin/pNFS export	2012-05-21 12:24:01 +03:00
Kconfig
Kconfig.ore
namei.c	vfs: check i_nlink limits in vfs_{mkdir,rename_dir,link}	2012-03-20 21:29:32 -04:00
ore_raid.c	ore: Unlock r4w pages in exact reverse order of locking	2012-07-20 11:49:25 +03:00
ore_raid.h
ore.c	ore: Remove support of partial IO request (NFS crash)	2012-07-20 11:47:43 +03:00
super.c	exofs: Add SYSFS info for autologin/pNFS export	2012-05-21 12:24:01 +03:00
symlink.c
sys.c	exofs: fix sparse non-ANSI function warning	2012-06-12 06:33:22 +03:00