© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
CryFS 0.9.10 fixed a dead lock and a race condition, the latter of which can cause data loss if the file system is under heavy load and accessed concurrently.
Changelog: https:/
Some user reports about the data loss:
- https:/
- https:/
- https:/
This issue is fixed in 0.9.10 but stable Ubuntu versions (bionic, cosmic) still distribute 0.9.9.
The package should be updated in the software repositories.
Notes:
- A 0.9.10 package is already in Debian and Ubuntu Disco, see https:/
- Debian will soon update to 0.10, and Ubuntu Disco is expected to follow. However, older Ubuntu versions should not update to 0.10.0 but only to 0.9.10 to fix the data loss bug.
- CryFS has an extensive test suite testing each release, the regression risk is low.
[Test Case]
Follow the instructions in the linked GitHub issues. Since this is a race condition, it doesn't always manifest, but https:/
1. Create a cryfs file system
$ cryfs -f /tmp/basedir /tmp/mountdir
Note: the '-f' causes CryFS to run in foreground, i.e. you won't get your terminal back. Keep it running and open a new terminal for the next commands.
2. Create a video file in the mounted directory
$ ffmpeg -i some_video_file.mp4 /tmp/mountdir/
3. Open /tmp/mountdir/
$ vlc /tmp/mountdir/
4. While it is running, re-create it
$ ffmpeg -i some_video_file.mp4 /tmp/mountdir/
5. Observe the crash in the terminal running the CryFS process
[Regression Potential]
The race condition was fixed in 0.9.10 using additional mutexes, so the most likely regression is the introduction of a new deadlock.
Generally, CryFS has a very extensive test suite and CI that is run on each commit and each release, see https:/