ubik: locking in recovery.c
authorMarc Dionne <marc.c.dionne@gmail.com>
Sat, 29 Jan 2011 19:37:23 +0000 (14:37 -0500)
committerDerrick Brashear <shadow@dementia.org>
Wed, 27 Apr 2011 00:36:33 +0000 (17:36 -0700)
commit89cdb34920e2e01adf045611ffd4d94abdbef87a
tree1753f7694f517c831db0b3f1352d2da15e0624b3
parent44801d157e6fd0933f37f0fc6451e37bdca285f3
ubik: locking in recovery.c

Locking changes in recovery.c:
- In urecovery_Initialize, hold the DB lock over ReplayLog
and InitializeDB
- Hold the DB lock over larger portions of urecovery_interact.
Some values which should be protected were examined and modified
without holding any locks.
- In the early part of urecovery_interact, only take the DB lock
when it's really needed, now that some values are protected by other
locks.
- DoProbe is now called without the DB lock, so it doesn't need to
drop and re-aquire it.

Change-Id: I1899b672687f0ab0eb59c74ff802750cdc377ae6
Reviewed-on: http://gerrit.openafs.org/4524
Reviewed-by: Jeffrey Altman <jaltman@openafs.org>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Derrick Brashear <shadow@dementia.org>
src/ubik/recovery.c