gocryptfs, branch master

fsync gocryptfs.diriv files

2026-09-01T20:38:37+00:00

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.diriv

2026-09-01T20:38:37+00:00

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

build(deps): bump actions/setup-go from 6 to 7

2026-09-01T20:03:15+00:00

Bumps [actions/setup-go](https://github.com/actions/setup-go) from 6 to 7. - [Release notes](https://github.com/actions/setup-go/releases) - [Commits](https://github.com/actions/setup-go/compare/v6...v7) --- updated-dependencies: - dependency-name: actions/setup-go dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot]

plaintextnames: don't initialize nametransform

2026-09-01T19:37:42+00:00

We should never call it in -plaintextnames mode.

Update performance.txt

2026-09-01T18:58:05+00:00

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

fusefrontend: make translateSize Stat_t/Statx_t agnostic

2026-07-22T19:51:40+00:00

sharedstorage: fix darwin & freebsd build failure

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