Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=unlinked_fsync 2026-09-01T20:38:37+00:00 2026-09-01T20:38:37+00:00 Jakob Unterwurzacher 2026-09-01T20:26:12+00:00 urn: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 2026-08-30T20:49:34+00:00 max 2026-08-17T01:15:41+00:00 urn: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 2026-07-22T19:57:57+00:00 Marios Titas 2026-07-21T17:27:38+00:00 urn: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 2026-07-22T19:51:40+00:00 Jakob Unterwurzacher 2026-07-22T19:49:43+00:00 urn:sha1:b3b292a8a3c1478b769e213e0e590f38cb1b923c 2026-07-16T20:07:54+00:00 Jakob Unterwurzacher 2026-07-16T19:10:14+00:00 urn:sha1:ace4b17c63d8d891227fce33ed36569db9472159 2026-07-16T20:07:54+00:00 Jakob Unterwurzacher 2026-07-16T19:01:01+00:00 urn:sha1:67e9abeb2830c517cbcbbd93de184055b2d4227b ...and one typo. 2026-07-16T20:07:54+00:00 Jakob Unterwurzacher 2026-07-16T18:47:57+00:00 urn:sha1:b89f0dc94bd83857b187a84a0d4ae127000f0b1c 2026-07-16T20:07:54+00:00 Jakob Unterwurzacher 2026-07-16T18:34:11+00:00 urn:sha1:bb68ca2aa7da9e166dca45979ff9932e05248370 2026-07-16T20:07:54+00:00 Jakob Unterwurzacher 2026-07-16T18:32:51+00:00 urn:sha1:a95d6ac5818a749db67d34bcbe9a358d403b6a6e 2026-07-16T20:07:54+00:00 Jakob Unterwurzacher 2024-12-30T11:08:41+00:00 urn:sha1:29000177b94c6c9aaab97b3f3d8ed5123ed7cf44 Prevent reads and writes concurrent with the truncate operation. It's racy on tmpfs and ext4 ( https://lore.kernel.org/all/18e9fa0f-ec31-9107-459c-ae1694503f87@gmail.com/t/ ) as evident by TestOpenTruncate test failures: === RUN TestOpenTruncate cluster_test.go:209: POSIX compliance issue: non-exlusive create failed with err=file exists doRead 16384215: corrupt block #0: cipher: message authentication failed ino16384215 fh8: RMW read failed: errno=5 cluster_test.go:214: iteration 1: WriteAt: write /tmp/gocryptfs-test-parent-1026/1358464214/TestOpenTruncate.1788296708.mnt2/foo: input/output error --- FAIL: TestOpenTruncate (0.06s) FAIL exit status 1 FAIL github.com/rfjakob/gocryptfs/v2/tests/cluster 7.880s Relates-to: https://github.com/rfjakob/gocryptfs/issues/56