ocfs2: Do not initialize lvb in ocfs2_orphan_scan_lock_res_init()
authorSunil Mushran <sunil.mushran@oracle.com>
Fri, 19 Jun 2009 23:53:18 +0000 (16:53 -0700)
committerJoel Becker <joel.becker@oracle.com>
Mon, 22 Jun 2009 21:24:53 +0000 (14:24 -0700)
commit3211949f8998dde71d9fe2e063de045ece5e0473
tree3aed155421642a6e04c94e0c5c521dea54e0b029
parent692684e19e317a374c18e70a44d6413e51f71c11
ocfs2: Do not initialize lvb in ocfs2_orphan_scan_lock_res_init()

We don't access the LVB in our ocfs2_*_lock_res_init() functions.

Since the LVB can become invalid during some cluster recovery
operations, the dlmglue must be able to handle an uninitialized
LVB.

For the orphan scan lock, we initialized an uninitialzed LVB with our
scan sequence number plus one.  This starts a normal orphan scan
cycle.

Signed-off-by: Sunil Mushran <sunil.mushran@oracle.com>
Signed-off-by: Joel Becker <joel.becker@oracle.com>
fs/ocfs2/dlmglue.c
fs/ocfs2/journal.c