gocryptfs/internal/fusefrontend, branch v2.5.0Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v2.5.02024-11-11T21:33:07+00:00Report inode number for the root node2024-11-11T21:33:07+00:00Jakob Unterwurzacher2024-11-11T21:27:42+00:00urn: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
fusefrontend: fix excessive file fragmentation on BTRFS2024-03-09T20:32:48+00:00Alex Shumsky2024-03-07T20:33:11+00:00urn:sha1:1d7dd0a76c15cf8c0dffef918a6b6c3dcb6347c4fusefrontend: implement our own Access()2023-05-17T21:26:56+00:00Jakob Unterwurzacher2023-05-17T21:26:56+00:00urn:sha1:09954c4bdecf0ca6da65776f176dc934ffced2b0
Not having Access() means go-fuse emulates it by looking at Getattr().
This works fine most of the time, but breaks down on sshfs, where
sshfs-benchmark.bash shows this:
gocryptfs/tests$ ./sshfs-benchmark.bash nuetzlich.net
working directory: /tmp/sshfs-benchmark.bash.JQC
sshfs mounted: nuetzlich.net:/tmp -> sshfs.mnt
gocryptfs mounted: sshfs.mnt/sshfs-benchmark.bash.Wrz/gocryptfs.crypt -> gocryptfs.mnt
sshfs-benchmark.bash: sshfs gocryptfs-on-sshfs
git init 3.98 6.80
rsync 7.71 10.84
rm -R 4.30rm: descend into write-protected directory 'gocryptfs.mnt/git1'?
The go-fuse emulation gets it wrong here because sshfs reports
permissions but does not enforce them.
Implement it ourselves properly.
fusefrontent: report correct size on hard link creation2023-03-29T20:16:14+00:00Jakob Unterwurzacher2023-03-29T20:16:14+00:00urn:sha1:24b3978715186bed3edc2703e81f165a73c0a74a
And add a test for it.
Fixes https://github.com/rfjakob/gocryptfs/issues/724
fusefrontend: unbreak isConsecutiveWrite streaming write optimization2023-02-21T21:08:41+00:00Jakob Unterwurzacher2023-02-21T21:04:30+00:00urn:sha1:8f3ec5dcaa6eb18d11746675190a7aaceb422764
Commit 6196a5b5 got the logic inverted, hence we never
set the last position markers.
Fixes https://github.com/rfjakob/gocryptfs/issues/712
fusefrontend: doWrite: report readFileID errors as I/O error2023-02-21T21:08:41+00:00Jakob Unterwurzacher2023-01-24T21:07:28+00:00urn:sha1:85297cda97d018b514361a2088a78f50f1446f95
It used to be reported as "function not implemented", accompanied
with this log output:
go-fuse: can't convert error type: ParseHeader: header is all-zero. Header hexdump: 000000000000000000000000000000000000
Now we report EIO and log this:
doWrite 1372183: corrupt header: ParseHeader: header is all-zero. Header hexdump: 000000000000000000000000000000000000
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:e9ecff7f07aeb1efe0edec7b4b050ce3c0ef75f8fusefrontend: support RENAME_WHITEOUT, RENAME_EXCHANGE2022-01-22T11:28:27+00:00Jakob Unterwurzacher2022-01-22T11:28:27+00:00urn:sha1:b7cac4ffd07733ab6bcd0d33345de3306a8a5a59
Both new internal test and xfstests generic/013 are happy.
https://github.com/rfjakob/gocryptfs/issues/641
fusefrontend: fix -force_owner not affecting MKNOD2022-01-10T19:05:36+00:00Jakob Unterwurzacher2022-01-10T19:05:36+00:00urn:sha1:5f955423b736d56b5b741fbd1b853c83044aa0fe
Fixes https://github.com/rfjakob/gocryptfs/issues/629