Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.3.2 2021-08-30T07:41:38+00:00 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/% 2019-09-08T19:19:44+00:00 Jakob Unterwurzacher 2019-09-08T19:19:44+00:00 urn:sha1:56eb85651be098fe810066f637c10004a7bea19b Found while debugging https://github.com/rfjakob/gocryptfs/pull/413 2017-04-29T12:50:58+00:00 Jakob Unterwurzacher 2017-04-29T12:50:58+00:00 urn:sha1:edb3e19cb5543c580261052395d461fa47c7cf58 2017-03-18T15:18:00+00:00 Jakob Unterwurzacher 2017-03-18T15:01:50+00:00 urn:sha1:00df0771e3dd9fba0992cbc9a7d347f25aff856a Due to kernel readahead, we usually get multiple read requests at the same time. These get submitted to the backing storage in random order, which is a problem if seeking is very expensive. Details: https://github.com/rfjakob/gocryptfs/issues/92