gocryptfs/internal/fusefrontend_reverse, branch xattr_user_buffer

Use user-provided Listxattr buffer size

2026-02-03T19:28:10+00:00

This huge buffer showed up big time in ./profiling/ls.bash and caused a 2x LS benchmark slowdown. Instead of the fixed-size buffer, use the buffer size hint the user has provided us. We return inaccurate (larger than actual, which should be safe) numbers when the user has provided no buffer (size probe).

added -noxattr flag which ignores all xattr operations (#987)

2026-01-18T18:48:51+00:00

* added -noxattr flag which ignores all xattr operations

Xattrs support in reverse mode

2025-11-22T20:24:20+00:00

Fixes https://github.com/rfjakob/gocryptfs/issues/827

Fix all staticcheck errors in gocryptfs codebase

2025-07-08T17:54:14+00:00

Co-authored-by: rfjakob <286847+rfjakob@users.noreply.github.com> Add staticcheck to test.bash for continuous static analysis Co-authored-by: rfjakob <286847+rfjakob@users.noreply.github.com> Fix nil pointer dereference in timesToTimespec function The previous fix for deprecated fuse.UtimeToTimespec caused a panic because unix.TimeToTimespec doesn't handle nil pointers. This fix properly handles nil pointers by using unix.UTIME_OMIT while still using the non-deprecated unix.TimeToTimespec function. Co-authored-by: rfjakob <286847+rfjakob@users.noreply.github.com> Undo SA6002 changes and add staticcheck ignore directive instead Co-authored-by: rfjakob <286847+rfjakob@users.noreply.github.com>

Fix a bunch of staticcheck errors

2025-07-07T17:59:35+00:00

Tool-assisted.

Switch to the new atomic Uint64.Add api

2025-05-06T07:11:49+00:00

The new api guarantees that the value is aligned, preventing stuff like this on 32 bit platforms: goroutine 26 [running]: internal/runtime/atomic.panicUnaligned() /usr/lib/go-1.24/src/internal/runtime/atomic/unaligned.go:8 +0x24 internal/runtime/atomic.Xadd64(0x2496c74, 0x1) /usr/lib/go-1.24/src/internal/runtime/atomic/atomic_arm.s:318 +0x14 github.com/rfjakob/gocryptfs/internal/inomap.(*InoMap).NextSpillIno(0x2496c60) Fixes https://github.com/rfjakob/gocryptfs/issues/912

fusefrontend_reverse: import go-gitignore with explicit alias

2025-05-06T07:07:54+00:00

reverse: lookupDiriv: use deriveDirIV helper

2025-01-18T18:57:44+00:00

reverse: advance mtime & ctime for virtual files by 10 seconds

2025-01-18T13:13:52+00:00

With inode number reuse and hard links, we could have returned wrong data for gocryptfs.diriv and gocryptfs.xyz.longname files, respectively (https://github.com/rfjakob/gocryptfs/issues/802). Now that this is fixed, ensure that rsync and similar tools pick up the new correct files by advancing mtime and ctime by 10 seconds, which should be more than any filesytems' timestamp granularity (FAT32 has 2 seconds).

Report inode number for the root node

2024-11-11T21:33:07+00:00

Now that https://github.com/hanwen/go-fuse/issues/399 has landed we can report an inode number for the root node. Fixes https://github.com/rfjakob/gocryptfs/issues/580