dlm: record full callback state
authorDavid Teigland <teigland@redhat.com>
Mon, 21 Feb 2011 20:58:21 +0000 (14:58 -0600)
committerDavid Teigland <teigland@redhat.com>
Thu, 10 Mar 2011 16:40:00 +0000 (10:40 -0600)
commit8304d6f24cc1221392b6d61fa9d16631cbd6beb7
treeca9b333d500d2fc56a45263aa08c4093875cbe12
parent35d34df711e8b44846e759d8cfddb4ec6877cccb
dlm: record full callback state

Change how callbacks are recorded for locks.  Previously, information
about multiple callbacks was combined into a couple of variables that
indicated what the end result should be.  In some situations, we
could not tell from this combined state what the exact sequence of
callbacks were, and would end up either delivering the callbacks in
the wrong order, or suppress redundant callbacks incorrectly.  This
new approach records all the data for each callback, leaving no
uncertainty about what needs to be delivered.

Signed-off-by: David Teigland <teigland@redhat.com>
fs/dlm/ast.c
fs/dlm/ast.h
fs/dlm/debug_fs.c
fs/dlm/dlm_internal.h
fs/dlm/lock.c
fs/dlm/rcom.c
fs/dlm/user.c
fs/dlm/user.h