aboutsummaryrefslogtreecommitdiff
path: root/Annex
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-10-17 12:56:26 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-10-17 13:58:43 -0400
commit873f698d40ed95d7875fb4b07cada3f4cbd3724e (patch)
tree4b099f7e86bf471482bb82d90dc6a99cd18a2258 /Annex
parentac598ce29a0dfe37c730b2d21d92d4c5b93da9ad (diff)
lock: Fix edge cases where data loss could occur in v6 mode.
In the case where the pointer file is in place, and not the content of the object, lock's performNew was called with filemodified=True, which caused it to try to repopulate the object from an unmodified associated file, of which there were none. So, the content of the object got thrown away incorrectly. This was the cause (although not the root cause) of data loss in https://github.com/datalad/datalad/issues/1020 The same problem could also occur when the work tree file is modified, but the object is not, and lock is called with --force. Added a test case for this, since it's excercising the same code path and is easier to set up than the problem above. Note that this only occurred when the keys database did not have an inode cache recorded for the annex object. Normally, the annex object would be in there, but there are of course circumstances where the inode cache is out of sync with reality, since it's only a cache. Fixed by checking if the object is unmodified; if so we don't need to try to repopulate it. This does add an additional checksum to the unlock path, but it's already checksumming the worktree file in another case, so it doesn't slow it down overall. Further investigation found a similar problem occurred when smudge --clean is called on a file and the inode cache is not populated. cleanOldKeys deleted the unmodified old object file in this case. This was also fixed by checking if the object is unmodified. In general, use of getInodeCaches and sameInodeCache is potentially dangerous if the inode cache has not gotten populated for some reason. Better to use isUnmodified. I breifly auited other places that check the inode cache, and did not see any immediate problems, but it would be easy to miss this kind of problem.
Diffstat (limited to 'Annex')
-rw-r--r--Annex/Ingest.hs7
1 files changed, 3 insertions, 4 deletions
diff --git a/Annex/Ingest.hs b/Annex/Ingest.hs
index 7b1db8aa7..c120f1a4d 100644
--- a/Annex/Ingest.hs
+++ b/Annex/Ingest.hs
@@ -244,10 +244,9 @@ cleanOldKeys file newkey = do
topf <- inRepo (toTopFilePath file)
oldkeys <- filter (/= newkey)
<$> Database.Keys.getAssociatedKey topf
- forM_ oldkeys $ \key -> do
- obj <- calcRepo (gitAnnexLocation key)
- caches <- Database.Keys.getInodeCaches key
- unlessM (sameInodeCache obj caches) $ do
+ forM_ oldkeys $ \key ->
+ unlessM (isUnmodified key =<< calcRepo (gitAnnexLocation key)) $ do
+ caches <- Database.Keys.getInodeCaches key
unlinkAnnex key
fs <- filter (/= ingestedf)
. map (`fromTopFilePath` g)