[DLM] fix lost flags in stub replies
authorDavid Teigland <teigland@redhat.com>
Wed, 13 Dec 2006 16:40:26 +0000 (10:40 -0600)
committerSteven Whitehouse <swhiteho@redhat.com>
Mon, 5 Feb 2007 18:36:02 +0000 (13:36 -0500)
commit075529b5e1ffa8c9864d23930b71b5306a13d9f8
tree414833bf6041a82f9e0cd2f813b05fe2da37ead8
parent8d07fd509e9c82a59e37b8b18a2fd0e8ef8fc837
[DLM] fix lost flags in stub replies

When the dlm fakes an unlock/cancel reply from a failed node using a stub
message struct, it wasn't setting the flags in the stub message.  So, in
the process of receiving the fake message the lkb flags would be updated
and cleared from the zero flags in the message.  The problem observed in
tests was the loss of the USER flag which caused the dlm to think a user
lock was a kernel lock and subsequently fail an assertion checking the
validity of the ast/callback field.

Signed-off-by: David Teigland <teigland@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
fs/dlm/lock.c