ubik: check if epoch is sane before db relabel 40/12640/3
authorMarcio Barbosa <mbarbosa@sinenomine.net>
Wed, 21 Jun 2017 20:24:05 +0000 (16:24 -0400)
committerBenjamin Kaduk <kaduk@mit.edu>
Fri, 26 Jan 2018 14:31:35 +0000 (09:31 -0500)
commitf5c289d00aaf7c5525b477da5b89f6675456c211
tree078c9934e7bb51c9ab1a469b463d4b962d927cf6
parent50c1d1088d2adcbb37b6a9d23fdd63617b1267be
ubik: check if epoch is sane before db relabel

The sync-site relabels its database at the end of the first write
transaction. The new label will be equal to the time at which the
sync-site in question first received its coordinator mandate. This time
is stored by a global called ubik_epochTime. In order to make sure that
the new database label is sane, only relabel the database if
ubik_epochTime is within a specific range.

Change-Id: I2408569e5de46d387f63cbc2fab05ea1264a505c
Reviewed-on: https://gerrit.openafs.org/12640
Reviewed-by: Mark Vitale <mvitale@sinenomine.net>
Reviewed-by: Andrew Deason <adeason@dson.org>
Reviewed-by: Benjamin Kaduk <kaduk@mit.edu>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
src/ubik/disk.c
src/ubik/ubik.p.h