gocryptfs/internal/fusefrontend_reverse, branch github_macos Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=github_macos 2025-07-08T17:54:14+00:00 Fix all staticcheck errors in gocryptfs codebase 2025-07-08T17:54:14+00:00 copilot-swe-agent[bot] 2025-07-07T18:18:12+00:00 urn:sha1:386232f39ede046d6453a0990ad40f2d86a26f53 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 Jakob Unterwurzacher 2025-07-07T17:54:48+00:00 urn:sha1:8f5df19b353e02ffba842fd1b15ccf93da7ee3b4 Tool-assisted. Switch to the new atomic Uint64.Add api 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 fusefrontend_reverse: import go-gitignore with explicit alias 2025-05-06T07:07:54+00:00 Jakob Unterwurzacher 2025-05-06T07:07:54+00:00 urn:sha1:e59f97806b12d593b972bbd17988f061fcc09043 reverse: lookupDiriv: use deriveDirIV helper 2025-01-18T18:57:44+00:00 Jakob Unterwurzacher 2025-01-14T19:04:17+00:00 urn:sha1:f93fa965b37926c6c5ad5ffdcfddaa131879f97f reverse: advance mtime & ctime for virtual files by 10 seconds 2025-01-18T13:13:52+00:00 Jakob Unterwurzacher 2025-01-18T13:11:51+00:00 urn:sha1:9eb47cf546d7e2499eab210d70050ef78087475a 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 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 reverse: fix import sorting in root_node.go 2024-11-11T21:33:07+00:00 Jakob Unterwurzacher 2024-11-11T21:26:55+00:00 urn:sha1:12c0f3a0bdd11444b8bf880af7c63ea7850391f2 reverse: fix force_owner 2024-08-23T20:32:46+00:00 Jakob Unterwurzacher 2024-08-23T20:32:46+00:00 urn:sha1:f665be1178c72a4768e82bccdfa073a0cf309215 Fixes https://github.com/rfjakob/gocryptfs/issues/809 reverse: use incrementing inode number for gocryptfs.longname.*.name files 2024-05-05T20:46:17+00:00 Jakob Unterwurzacher 2024-05-05T20:46:17+00:00 urn:sha1:a38507978442f28ace42ec0003c4a2bf61cb4a91 ed0a12b7337c2d88c027329f64e73070da17d5b3 already fixed the kernel side, now we also want the .name files to NOT appear hardlinked when just looking at the inode number. Relates-to: https://github.com/rfjakob/gocryptfs/issues/802