gocryptfs/internal/fusefrontend/names.go, branch xattr_user_buffer Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer 2019-01-02T20:52:52+00:00 fusefrontend: move openBackingDir into its own file 2019-01-02T20:52:52+00:00 Jakob Unterwurzacher 2019-01-02T20:52:52+00:00 urn:sha1:352f3147c5f1260cf729692d945c87e210cb1ad8 This function is in all fastpaths, will get a cache, and needs its own file. renamed: internal/fusefrontend/names.go -> internal/fusefrontend/openbackingdir.go renamed: internal/fusefrontend/names_test.go -> internal/fusefrontend/openbackingdir_test.go fusefronted: make EncryptPath symlink-safe 2019-01-02T20:45:40+00:00 Jakob Unterwurzacher 2019-01-02T20:45:40+00:00 urn:sha1:2b12bba274ba75f76ac8c2af3790e4190b32396f Finally allows us to delete EncryptPathDirIV. fusefrontend: openBackingDir: fix fd leak in error path 2019-01-01T23:14:12+00:00 Jakob Unterwurzacher 2019-01-01T23:14:12+00:00 urn:sha1:5aa1755cbc55d17a5b4b71faa1e0bba34fe83d8b Reported by @slackner at https://github.com/rfjakob/gocryptfs/commit/932efbd4593fe6be6c86f0dafeaea32910b7c246#r31813373 thanks! fusefrontend: only compile getBackingPath() on Darwin 2019-01-01T15:24:25+00:00 Jakob Unterwurzacher 2018-11-11T17:32:48+00:00 urn:sha1:1d5500c3db3b4b1f5a5fbc49c7934d3665739a0a This function is NOT symlink-safe. Darwin needs it because it lacks fgetxattr(2) and friends. fusefrontend: make GetXAttr() symlink-safe on Linux 2019-01-01T15:24:25+00:00 Jakob Unterwurzacher 2018-11-11T16:43:48+00:00 urn:sha1:2286372603f506cf719654a9901de0749c544b12 Uses the /proc/self/fd trick, which does not work on Darwin. fusefrontend: mark a few more functions as symlink-safe / unsafe 2019-01-01T15:24:25+00:00 Jakob Unterwurzacher 2018-11-04T20:29:17+00:00 urn:sha1:de3a2c189578f7636c39fde44fbe1da9c78b367e fusefrontend: make openBackingDir() symlink-safe 2019-01-01T15:24:09+00:00 Jakob Unterwurzacher 2018-10-14T18:11:49+00:00 urn:sha1:932efbd4593fe6be6c86f0dafeaea32910b7c246 openBackingDir() used encryptPath(), which is not symlink-safe itself. Drop encryptPath() and implement our own directory walk. Adds three seconds to untar and two seconds to rm: $ ./benchmark.bash Testing gocryptfs at /tmp/benchmark.bash.MzG: gocryptfs v1.6-36-g8fb3c2f-dirty; go-fuse v20170619-66-g6df8ddc; 2018-10-14 go1.11 WRITE: 262144000 bytes (262 MB, 250 MiB) copied, 1.25078 s, 210 MB/s READ: 262144000 bytes (262 MB, 250 MiB) copied, 1.0318 s, 254 MB/s UNTAR: 20.941 MD5: 11.568 LS: 1.638 RM: 5.337 Add option for autounmount 2018-10-11T18:16:45+00:00 Jesse Dunietz 2018-10-06T19:49:33+00:00 urn:sha1:87d3ed9187cb9caccaa8df0769d4cb722cc5bd00 Even though filesystem notifications aren't implemented for FUSE, I decided to try my hand at implementing the autounmount feature (#128). I based it on the EncFS autounmount code, which records filesystem accesses and checks every X seconds whether it's idled long enough to unmount. I've tested the feature locally, but I haven't added any tests for this flag. I also haven't worked with Go before. So please let me know if there's anything that should be done differently. One particular concern: I worked from the assumption that the open files table is unique per-filesystem. If that's not true, I'll need to add an open file count and associated lock to the Filesystem type instead. https://github.com/rfjakob/gocryptfs/pull/265 fusefrontend: add named parameters to openBackingDir 2018-09-23T10:17:59+00:00 Jakob Unterwurzacher 2018-09-22T18:25:47+00:00 urn:sha1:bead82c9fb91cbae0290523b57eec421e5218177 Named parameters make using the function easier. fusefrontend: get rid of os.File* wrapping 2018-09-23T10:17:26+00:00 Jakob Unterwurzacher 2018-09-22T18:10:34+00:00 urn:sha1:c270b21efc1d9ecbe5c913c733204f826e263747 Directly use int file descriptors for the dirfd and get rid of one level of indirection.