gocryptfs/internal/inomap, branch go-git-gitignoreMirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=go-git-gitignore2025-05-06T07:11:49+00:00Switch to the new atomic Uint64.Add api2025-05-06T07:11:49+00:00Jakob Unterwurzacher2025-05-06T07:11:49+00:00urn: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
inomap: export NextSpillIno()2024-05-05T20:25:19+00:00Jakob Unterwurzacher2024-05-05T20:25:19+00:00urn:sha1:5a2d4614ed75d4b32e0f45e93a225f8e1b7350c9
This will be used in reverse mode. Switch to atomic increment to avoid
a "nextSpillInoUnlocked" helper.
inomap: incorporate spillBit into the spillNext start value2024-05-05T20:05:08+00:00Jakob Unterwurzacher2024-05-05T20:05:08+00:00urn:sha1:c85c092189df44e9a88ad30c1f91cfc7fbeb4ccb
This avoids the manual "| spillBit" logic.
make format2022-12-29T14:00:37+00:00Jakob Unterwurzacher2022-12-29T14:00:24+00:00urn:sha1:856ccaac10579abda5620dfc86ad6031b1076a43
Run "make format" using
go version go1.19.4 linux/amd64
Fix typos2022-06-26T08:59:06+00:00Yuta Hayashibe2022-05-04T09:06:20+00:00urn:sha1:e9ecff7f07aeb1efe0edec7b4b050ce3c0ef75f8inomap: deterministically set root device2021-09-10T15:17:16+00:00Jakob Unterwurzacher2021-09-10T15:17:16+00:00urn: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.
go mod: declare module version v22021-08-23T13:05:15+00:00Jakob Unterwurzacher2021-08-23T13:05:15+00:00urn: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/%
inomap: update outdated wording in comments2021-08-16T15:14:14+00:00Jakob Unterwurzacher2021-08-16T15:14:14+00:00urn:sha1:763499ee80f5acb7ab1db70d86c65485bebb115einomap: warn on first use of spillMap2021-08-16T15:13:14+00:00Jakob Unterwurzacher2021-08-16T15:13:14+00:00urn:sha1:b8d78d6a3153f0ebf01e11426bd28453c7b8b522
We normally should not need it, warn if we do.
As the tests run with -wpanic, we would catch it.
fusefrontend: -sharedstorage: present stable inode numbers2021-07-31T11:24:25+00:00Jakob Unterwurzacher2021-07-31T11:24:25+00:00urn:sha1:1bc1db620b061aabf59469a5eb4fb60e3e1701a3
Use the Gen field (inode generation) to distinguish hard links
while passing the real inode numbers to userspace.
Fixes https://github.com/rfjakob/gocryptfs/issues/584