gocryptfs/internal, branch unlinked_fsyncMirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=unlinked_fsync2026-09-01T20:38:37+00:00fsync gocryptfs.diriv files2026-09-01T20:38:37+00:00Jakob Unterwurzacher2026-09-01T20:35:45+00:00urn:sha1:842af4463989ee6808d397433e9aba8517e49c89
There is a performance penalty here, but the alternative is
potential data loss on a system crash / power outage as shown in
https://github.com/rfjakob/gocryptfs/issues/1033 .
Also deduplicate the code a little using goto.
Fixes https://github.com/rfjakob/gocryptfs/issues/1033
fusefronted: fix mkdir log message on empty gocryptfs.diriv2026-09-01T20:38:37+00:00Jakob Unterwurzacher2026-09-01T20:26:12+00:00urn:sha1:c7f1fe301a43604cb2eb9d67f389563e8734016c
Before:
$ mkdir asd
mkdir: cannot create directory ‘asd’: Operation not supported
Sep 01 22:24:15 brikett gocryptfs[185344]: go-fuse: can't convert error type: wanted 16 bytes, got 0
After:
$ mkdir asdasd
mkdir: cannot create directory ‘asdasd’: Input/output error
Sep 01 22:25:00 brikett gocryptfs[185784]: prepareAtSyscall: could not read gocryptfs.diriv: wanted 16 bytes, got 0
https://github.com/rfjakob/gocryptfs/issues/1033
plaintextnames: don't initialize nametransform2026-09-01T19:37:42+00:00Jakob Unterwurzacher2026-09-01T19:36:57+00:00urn:sha1:12fa2c54de65e57649e07042b6cf517896a430aa
We should never call it in -plaintextnames mode.
fusefrontend: take ContentLock for truncate through node.Setattr2026-08-30T20:49:34+00:00max2026-08-17T01:15:41+00:00urn:sha1:9c2130d6c2e54c45c6787fbc49a896a8544a5e47
node.Setattr opens its own file handle and called truncate directly,
without ContentLock. truncate ends in doWrite, which documents that the
caller holds that lock, and file.Setattr and Allocate both take it.
Besides leaving a path truncate unserialized against concurrent writes,
this skipped the write-operation counter that ContentLock.Lock()
increments. isConsecutiveWrite() reads that counter to notice foreign
modifications, so an already-open handle kept assuming its next write
appends, skipped writePadHole() and grew the file past a short last
block. That block no longer decrypted, and every later operation on the
file failed with EIO.
Fixes #1024
fusefrontend: expose birth time via statx2026-07-22T19:57:57+00:00Marios Titas2026-07-21T17:27:38+00:00urn:sha1:790362e8f8eabd1bdf75f98328daf94cf623c600
Forward the backing filesystem's STATX_BTIME on Linux while preserving
existing metadata translations and fallback behavior.
On Linux 6.6 and newer, this allows statx consumers such as GNU stat
to report birth time when the backing filesystem provides it. Older
kernels and backing filesystems without birth-time support retain the
existing behavior. No on-disk format change or migration is required.
Reverse mode remains unchanged.
Fixes #868.
Related context: #732
fusefrontend: make translateSize Stat_t/Statx_t agnostic2026-07-22T19:51:40+00:00Jakob Unterwurzacher2026-07-22T19:49:43+00:00urn:sha1:b3b292a8a3c1478b769e213e0e590f38cb1b923csharedstorage: fix darwin & freebsd build failure2026-07-16T20:07:54+00:00Jakob Unterwurzacher2026-07-16T19:16:45+00:00urn:sha1:b8e34b1efcb27c772f0d2ca12f5ecdd6b7fc817bfusefrontend: sharedstorage: truncate: error out on failed file lock2026-07-16T20:07:54+00:00Jakob Unterwurzacher2026-07-16T19:10:14+00:00urn:sha1:ace4b17c63d8d891227fce33ed36569db9472159tests/cluster: fix possible fd exhaustion2026-07-16T20:07:54+00:00Jakob Unterwurzacher2026-07-16T19:01:01+00:00urn:sha1:67e9abeb2830c517cbcbbd93de184055b2d4227b
...and one typo.
fusefrontend: LockSharedStorage: loop on EINTR, add debug output2026-07-16T20:07:54+00:00Jakob Unterwurzacher2026-07-16T18:47:57+00:00urn:sha1:b89f0dc94bd83857b187a84a0d4ae127000f0b1c