<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs/internal, branch v1.1.1</title>
<subtitle>Mirror of gocryptfs source code on Github</subtitle>
<id>http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.1.1</id>
<link rel='self' href='http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.1.1'/>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/'/>
<updated>2016-10-30T15:29:36+00:00</updated>
<entry>
<title>fusefrontend: drop atime workarounds</title>
<updated>2016-10-30T15:29:36+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-10-30T15:29:36+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=c2192cfcade7b6a165f32a1b7471dfb765e86e00'/>
<id>urn:sha1:c2192cfcade7b6a165f32a1b7471dfb765e86e00</id>
<content type='text'>
The fix at https://github.com/hanwen/go-fuse/pull/131 has been merged.
Drop the workarounds and re-enable the tests.
</content>
</entry>
<entry>
<title>fusefronted: more concise corrupt block log message</title>
<updated>2016-10-28T19:18:36+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-10-28T18:07:59+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=85f1fd0b0f16ea47e038584e7ff53894d508604a'/>
<id>urn:sha1:85f1fd0b0f16ea47e038584e7ff53894d508604a</id>
<content type='text'>
Calculating the block offset is easy enough, even more now
that gocryptfs-xray exists.
</content>
</entry>
<entry>
<title>fusefrontend: I/O error instead of panic on all-zero nonce</title>
<updated>2016-10-28T19:18:36+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-10-28T18:05:57+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=012152f3d1f111541f2fbb4c1e65c91243cd6bde'/>
<id>urn:sha1:012152f3d1f111541f2fbb4c1e65c91243cd6bde</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>fusefronted: optimize NFS streaming writes by saving one Stat()</title>
<updated>2016-10-28T19:17:53+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-10-25T21:57:30+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=a08d55f42d5b11e265a8617bee16babceebfd026'/>
<id>urn:sha1:a08d55f42d5b11e265a8617bee16babceebfd026</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>fusefrontend: move hole padding check out of Write()</title>
<updated>2016-10-25T20:37:45+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-10-25T20:37:45+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=d64ccf7cf4d110d515b07b7f95127f12ecd4d318'/>
<id>urn:sha1:d64ccf7cf4d110d515b07b7f95127f12ecd4d318</id>
<content type='text'>
The details of the hole handling don't have to be in
Write, so move it away.
</content>
</entry>
<entry>
<title>fusefrontend: rename "createsHole" to clearer "createsCiphertextHole"</title>
<updated>2016-10-25T19:19:37+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-10-25T19:19:37+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=6538dc15afb7a7a159f070a57a1e9073ca076661'/>
<id>urn:sha1:6538dc15afb7a7a159f070a57a1e9073ca076661</id>
<content type='text'>
...and add comments for what is happening.
</content>
</entry>
<entry>
<title>Fix misspellings</title>
<updated>2016-10-24T17:18:13+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-10-24T17:18:13+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=aeda9721d0150b9b77d9522bb3b4fcd17f2cbbfa'/>
<id>urn:sha1:aeda9721d0150b9b77d9522bb3b4fcd17f2cbbfa</id>
<content type='text'>
Close https://github.com/rfjakob/gocryptfs/issues/54
</content>
</entry>
<entry>
<title>configfile: add newline at the end</title>
<updated>2016-10-21T06:43:39+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-10-21T06:43:39+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=a74a7e7f547e021abc9b9fd956f3cae54d740dd3'/>
<id>urn:sha1:a74a7e7f547e021abc9b9fd956f3cae54d740dd3</id>
<content type='text'>
For convenience for the user, add a newline at the end.
Reported as #51 .
</content>
</entry>
<entry>
<title>tests: add 1980.tar.gz extract test</title>
<updated>2016-10-19T20:25:54+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-10-19T20:25:54+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=589748548f24429bb30a8aafb3cae0d295b07da0'/>
<id>urn:sha1:589748548f24429bb30a8aafb3cae0d295b07da0</id>
<content type='text'>
Test that we get the right timestamp when extracting a tarball.

Also simplify the workaround in doTestUtimesNano() and fix the
fact that it was running no test at all.
</content>
</entry>
<entry>
<title>lint fixes</title>
<updated>2016-10-18T23:12:45+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-10-18T23:12:45+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=600ceece359d835934ad039bdd0e83cd647c410f'/>
<id>urn:sha1:600ceece359d835934ad039bdd0e83cd647c410f</id>
<content type='text'>
</content>
</entry>
</feed>
