gocryptfs/tests, branch unlinked_fsync

tests: add TestUnlinkedO_SYNC

2026-09-24T18:45:57+00:00

Relates-to: #1023 https://github.com/rfjakob/gocryptfs/issues/1023

cli: use READDIR by default

2026-09-01T18:51:36+00:00

Avoid eager per-entry metadata work for names-only listings, and add -readdirplus for workloads that benefit from eager attributes. Co-authored-by: Cursor

fusefrontend: take ContentLock for truncate through node.Setattr

2026-08-30T20:49:34+00:00

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 statx

2026-07-22T19:57:57+00:00

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

sharedstorage: fix darwin & freebsd build failure

2026-07-16T20:07:54+00:00

tests/cluster: fix possible fd exhaustion

2026-07-16T20:07:54+00:00

...and one typo.

tests/cluster: enable TestClusterConcurrentRW per default

2026-07-16T20:07:54+00:00

Add the -sharedstorage flag to the mounts and make it more severe by adjusting the I/O and file sizes to arbitrary unaligned values. It passes *most of the time*. If it fails, it's like this, and the reason is that there is no fcntl locks in the READ path yet. gocryptfs/tests/cluster$ go test -run TestClusterConcurrentRW -v === RUN TestClusterConcurrentRW doRead 2895433: corrupt block #0: cipher: message authentication failed doRead 2895433: corrupt block #0: cipher: message authentication failed doRead 2895433: corrupt block #0: cipher: message authentication failed cluster_test.go:98: readThread iteration 9165: ReadAt failed: read /var/tmp/gocryptfs-test-parent-1026/3021427391/TestClusterConcurrentRW.366469887.mnt1/foo: input/output error --- FAIL: TestClusterConcurrentRW (0.40s) FAIL exit status 1 FAIL github.com/rfjakob/gocryptfs/v2/tests/cluster 0.406s

tests/cluster: add TestPoCTornWriteLocked

2026-07-16T20:07:54+00:00

tests/cluster: note that ext4 provides no atomicity

2026-07-16T20:07:54+00:00

tests/cluster: add TestPoCTornWrite

2026-07-16T20:07:54+00:00

Scary. But explains why TestConcurrentCreate fails. gocryptfs/tests/cluster$ go test -run TestPoCTornWrite --- FAIL: TestPoCTornWrite (0.00s) poc_test.go:210: iteration 214: inconsistent block: d6d6d6d6d6d6d6d6d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1 FAIL