ocfs2_dlm: fix cluster-wide refcounting of lock resources
This was previously broken and migration of some locks had to be temporarily disabled. We use a new (and backward-incompatible) set of network messages to account for all references to a lock resources held across the cluster. once these are all freed, the master node may then free the lock resource memory once its local references are dropped. Signed-off-by:Kurt Hackel <kurt.hackel@oracle.com> Signed-off-by:
Mark Fasheh <mark.fasheh@oracle.com>
Showing
- fs/ocfs2/cluster/tcp_internal.h 4 additions, 1 deletionfs/ocfs2/cluster/tcp_internal.h
- fs/ocfs2/dlm/dlmcommon.h 71 additions, 4 deletionsfs/ocfs2/dlm/dlmcommon.h
- fs/ocfs2/dlm/dlmdebug.c 18 additions, 0 deletionsfs/ocfs2/dlm/dlmdebug.c
- fs/ocfs2/dlm/dlmdomain.c 87 additions, 30 deletionsfs/ocfs2/dlm/dlmdomain.c
- fs/ocfs2/dlm/dlmlock.c 4 additions, 0 deletionsfs/ocfs2/dlm/dlmlock.c
- fs/ocfs2/dlm/dlmmaster.c 352 additions, 42 deletionsfs/ocfs2/dlm/dlmmaster.c
- fs/ocfs2/dlm/dlmrecovery.c 116 additions, 7 deletionsfs/ocfs2/dlm/dlmrecovery.c
- fs/ocfs2/dlm/dlmthread.c 77 additions, 90 deletionsfs/ocfs2/dlm/dlmthread.c
This diff is collapsed.
Please register or sign in to comment