When the lock master processes a successful operation (request,
convert, cancel, or unlock), it will process the effects of the
change before sending the reply for the operation. The effects
of the operation are:
- blocking callbacks (basts) for any newly granted locks
- waiting or converting
From: Steven Whitehouse swhit...@redhat.com
Although it is possible to get this information from the path,
its much easier to provide the lockspace as a seperate env
variable.
Signed-off-by: Steven Whitehouse swhit...@redhat.com
Signed-off-by: David Teigland teigl...@redhat.com
---
Hi,
Reposting the dlm patches for the 2.6.34 merge. The patch dlm: send
reply before bast is expanded slightly to cover the cancel and unlock
cases the same way that convert and request have been fixed. There's a
fourth patch added that makes the debugfs bast mode more useful for
debugging
The bast mode that appears in the debugfs output should be
useful on both master and process nodes. lkb_highbast is
currently printed, and is only useful on the master node.
lkb_bastmode is only useful on the process node. This
patch sets lkb_bastmode on the master node as well, and
uses that
When both blocking and completion callbacks are queued for lock,
the dlm would always deliver the completion callback (cast) first.
In some cases the blocking callback (bast) is queued before the
cast, though, and should be delivered first. This patch keeps
track of the order in which they were
