fsck --from remote -J concurrency bug

fsck --from remote: Fix a concurrency bug that could make it incorrectly
detect that content in the remote is corrupt, and remove it, resulting in
data loss.
This commit is contained in:
Joey Hess 2020-02-14 14:52:15 -04:00
parent 399319ccbc
commit 352963690a
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 23 additions and 2 deletions

View file

@ -145,3 +145,5 @@ whereis file2 (1 copy)
5d9b0df2-000b-4273-bc4a-fb3b9d8319bd -- testrepo [here]
ok
"""]]
> [[fixed|done]] --[[Joey]]

View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-02-14T18:49:07Z"
content="""
Ugh, I think this could potentially result in data loss. Not when using bup,
but other special remotes.
I've fixed it in git and will think about moving the date of the next
release up.
"""]]