linux/fs/gfs2/locking/dlm
Benjamin Marzinski 58e9fee13e [GFS2] Invalidate cache at correct point
GFS2 wasn't invalidating its cache before it called into the lock manager
with a request that could potentially drop a lock.  This was leaving a
window where the lock could be actually be held by another node, but the
file's page cache would still appear valid, causing coherency problems.
This patch moves the cache invalidation to before the lock manager call
when dropping a lock. It also adds the option to the lock_dlm lock
manager to not use conversion mode deadlock avoidance, which, on a
conversion from shared to exclusive, could internally drop the lock, and
then reacquire in. GFS2 now asks lock_dlm to not do this.  Instead, GFS2
manually drops the lock and reacquires it.

Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
2008-03-31 10:41:44 +01:00
..
lock_dlm.h [GFS2] proper extern for gfs2/locking/dlm/mount.c:gdlm_ops 2008-03-31 10:41:09 +01:00
lock.c [GFS2] Invalidate cache at correct point 2008-03-31 10:41:44 +01:00
main.c [GFS2] proper extern for gfs2/locking/dlm/mount.c:gdlm_ops 2008-03-31 10:41:09 +01:00
Makefile [GFS2] Fix bug in Makefiles for lock modules 2006-09-27 12:20:06 -04:00
mount.c [GFS2] tidy up error message 2008-01-25 08:08:04 +00:00
plock.c [GFS2] use pid for plock owner for nfs clients 2008-01-25 08:08:23 +00:00
sysfs.c [GFS2] proper extern for gfs2/locking/dlm/mount.c:gdlm_ops 2008-03-31 10:41:09 +01:00
thread.c [GFS2] Invalidate cache at correct point 2008-03-31 10:41:44 +01:00