gocryptfs, branch masterMirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=master2026-07-22T19:57:57+00:00fusefrontend: 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:b89f0dc94bd83857b187a84a0d4ae127000f0b1cfusefrontend: sharedstorage: add two missing unlocks2026-07-16T20:07:54+00:00Jakob Unterwurzacher2026-07-16T18:34:11+00:00urn:sha1:bb68ca2aa7da9e166dca45979ff9932e05248370fusefrontend: sharedstorage: introduce UnlockSharedStorage helper2026-07-16T20:07:54+00:00Jakob Unterwurzacher2026-07-16T18:32:51+00:00urn:sha1:a95d6ac5818a749db67d34bcbe9a358d403b6a6efusefrontend: sharedstorage: lock truncate agains concurrent access2026-07-16T20:07:54+00:00Jakob Unterwurzacher2024-12-30T11:08:41+00:00urn: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
fusefrontend: sharedstorage: add warnings for lock failure2026-07-16T20:07:54+00:00Jakob Unterwurzacher2023-06-19T11:35:29+00:00urn:sha1:836f4fc356ae860d8d3a323ada0bb0d71ed102bc
Complain loudly when the underlying storage does not support
byte-range locks.
https://github.com/rfjakob/gocryptfs/issues/754