Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer 2026-02-01T19:05:13+00:00 2026-02-01T19:05:13+00:00 Jakob Unterwurzacher 2026-02-01T19:05:13+00:00 urn:sha1:ed5f8487b15f1d9cd83b4b0a4220271b6c5f189e Reported by @Tunoac, https://github.com/rfjakob/gocryptfs/issues/395#issuecomment-3828507487 2025-05-29T19:38:25+00:00 Jakob Unterwurzacher 2025-05-29T19:30:53+00:00 urn:sha1:2609c72beee098c6afe4bbc3344a1fcee06df94b 2025-05-06T07:11:49+00:00 Jakob Unterwurzacher 2025-05-06T07:11:49+00:00 urn:sha1:9b6e47fc0a2ed65d462424152a13f995a8d7dd9a 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 2024-11-11T21:33:07+00:00 Jakob Unterwurzacher 2024-11-11T21:27:42+00:00 urn:sha1:86891054ef2a5d1b0b59c7c140aae284e7c5bd87 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 2021-12-19T13:43:56+00:00 Jakob Unterwurzacher 2021-12-19T13:43:56+00:00 urn:sha1:64be5de75f42e415198ff5e77de509680b69e0e1 xattr names have fewer restrictions than file names, relax the validation. Fixes https://github.com/rfjakob/gocryptfs/issues/627 2021-09-10T15:17:16+00:00 Jakob Unterwurzacher 2021-09-10T15:17:16+00:00 urn:sha1:c9b825c58a9f996379108926754513bca03bb306 We used to have "first Translate() wins". This is not deterministic, as the LOOKUP for the root directory does not seem to reach us, so the first user LOOKUP would win, which may be on a mountpoint. 2021-08-30T07:41:38+00:00 Jakob Unterwurzacher 2021-08-30T07:39:57+00:00 urn:sha1:b83ca9c921019fc3b790dabb6198bb77ef2f9a34 Will be replaced by go-fuse's new SyncRead flag. More info: https://github.com/hanwen/go-fuse/issues/395 SyncRead commit: https://github.com/hanwen/go-fuse/commit/15a8bb029a4e1a51e10043c370970596b1fbb737 2021-08-23T13:05:15+00:00 Jakob Unterwurzacher 2021-08-23T13:05:15+00:00 urn:sha1:69d88505fd7f4cb0d9e4f1918de296342fe05858 Our git version is v2+ for some time now, but go.mod still declared v1. Hopefully making both match makes https://pkg.go.dev/github.com/rfjakob/gocryptfs/v2 work. All the import paths have been fixed like this: find . -name \*.go | xargs sed -i s%github.com/rfjakob/gocryptfs/%github.com/rfjakob/gocryptfs/v2/% 2021-08-11T18:23:35+00:00 Jakob Unterwurzacher 2021-08-11T18:21:32+00:00 urn:sha1:2d386fc92e88be5384d1654db5d6e23ef4682354 We need to look at f_fstypename acc. to https://stackoverflow.com/a/52299141/1380267 : > As filesystem type numbers are now assigned at runtime in > recent versions of MacOS, you must use f_fstypename to > determine the type. https://github.com/rfjakob/gocryptfs/issues/585 2021-08-02T18:01:26+00:00 Jakob Unterwurzacher 2021-08-02T18:01:26+00:00 urn:sha1:c3c9513e6504276698ed1f50a259d4333476acf8 This also moves the quirks logic into fusefrontend. Fixes https://github.com/rfjakob/gocryptfs/issues/585