gocryptfs, branch v1.1.1 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.1.1 2016-10-30T15:48:02+00:00 Update README for v1.1.1 2016-10-30T15:48:02+00:00 Jakob Unterwurzacher 2016-10-30T15:48:02+00:00 urn:sha1:1a847b8f008d4f4105443b2b0fde2c17d145e820 fusefrontend: drop atime workarounds 2016-10-30T15:29:36+00:00 Jakob Unterwurzacher 2016-10-30T15:29:36+00:00 urn:sha1:c2192cfcade7b6a165f32a1b7471dfb765e86e00 The fix at https://github.com/hanwen/go-fuse/pull/131 has been merged. Drop the workarounds and re-enable the tests. build.bash: rename "GOPATH2" to "GOPATH1" 2016-10-30T15:17:39+00:00 Jakob Unterwurzacher 2016-10-30T15:13:16+00:00 urn:sha1:4e95d394cf23978db2baadcf34fac3483f717ebd It's the 1st component of GOPATH, so call it like that. build.bash: abort if we hit a known-bad go-fuse version 2016-10-30T15:17:00+00:00 Jakob Unterwurzacher 2016-10-30T15:10:40+00:00 urn:sha1:c7385b3681248d5935743c007d17fda724cc142f Also, standardize to "if [[ ]] ; then" style. fusefronted: more concise corrupt block log message 2016-10-28T19:18:36+00:00 Jakob Unterwurzacher 2016-10-28T18:07:59+00:00 urn:sha1:85f1fd0b0f16ea47e038584e7ff53894d508604a Calculating the block offset is easy enough, even more now that gocryptfs-xray exists. fusefrontend: I/O error instead of panic on all-zero nonce 2016-10-28T19:18:36+00:00 Jakob Unterwurzacher 2016-10-28T18:05:57+00:00 urn:sha1:012152f3d1f111541f2fbb4c1e65c91243cd6bde Running xfstests generic/075 on tmpfs often triggered a panic for what seems to be a tmpfs bug. Quoting from the email to lkml, http://www.spinics.net/lists/kernel/msg2370127.html : tmpfs seems to be incorrectly returning 0-bytes when reading from a file that is concurrently being truncated. main: redirect panics to /tmp/gocryptfs_panic.NNNN 2016-10-28T19:18:36+00:00 Jakob Unterwurzacher 2016-10-26T09:19:14+00:00 urn:sha1:4cc64c2c9579283da6a997c425e986dfe014c56d Redirect stdout and stderr to /tmp/gocryptfs_paniclog.NNNNNN instead of closing them so users have a chance to get the backtrace on a panic. This only applies if "-nosyslog" is NOT set. Panics will go to terminal as usual if it is. fusefronted: optimize NFS streaming writes by saving one Stat() 2016-10-28T19:17:53+00:00 Jakob Unterwurzacher 2016-10-25T21:57:30+00:00 urn:sha1:a08d55f42d5b11e265a8617bee16babceebfd026 Stat() calls are expensive on NFS as they need a full network round-trip. We detect when a write immediately follows the last one and skip the Stat in this case because the write cannot create a file hole. On my (slow) NAS, this takes the write speed from 24MB/s to 41MB/s. tests: fetch the example tarball from cdn.kernel.org 2016-10-25T21:13:44+00:00 Jakob Unterwurzacher 2016-10-25T21:13:44+00:00 urn:sha1:9b7135224bc3596ee3bceeca83cca3a687b0e9c7 www.kernel.org is painfully slow at times. fusefrontend: move hole padding check out of Write() 2016-10-25T20:37:45+00:00 Jakob Unterwurzacher 2016-10-25T20:37:45+00:00 urn:sha1:d64ccf7cf4d110d515b07b7f95127f12ecd4d318 The details of the hole handling don't have to be in Write, so move it away.