Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.0-beta3 2021-04-02T18:22:26+00:00 2021-04-02T18:22:26+00:00 Jakob Unterwurzacher 2021-04-02T18:22:26+00:00 urn:sha1:beab7004f2556fec637ebe55a3aefad3d81c419f With 1.0 seconds we see failures on Travis, example: https://travis-ci.org/github/rfjakob/gocryptfs/builds/765648739 With 1.1 seconds it seems to always work. 2021-03-30T13:11:28+00:00 Jakob Unterwurzacher 2021-03-30T12:58:18+00:00 urn:sha1:a2effaae390253bfbc2e9522dd4b5123a067f60f 2021-03-21T10:10:18+00:00 Jakob Unterwurzacher 2021-03-21T10:10:18+00:00 urn:sha1:d7d79aa81c6d8f07e8b5c3f689b528462f32daa0 Towards better test coverage of shared backing storage mounts. https://github.com/rfjakob/gocryptfs/issues/525 2021-03-21T09:53:51+00:00 Jakob Unterwurzacher 2021-03-21T09:53:51+00:00 urn:sha1:6da2a690187f404031862d56804537649cb4a2ab The inode number is not stable with `-sharedstorage`. Ignore it. Failure was like this: --- FAIL: TestFallocate (0.02s) helpers.go:229: Stat vs Fstat mismatch: st= {59 11543 1 33188 1026 1026 0 0 0 4096 8 {1616315569 838232716} {1616315569 838232716} {1616315569 838232716} [0 0 0]} st2={59 11545 1 33188 1026 1026 0 0 0 4096 8 {1616315569 838232716} {1616315569 838232716} {1616315569 838232716} [0 0 0]} 2021-03-20T17:27:34+00:00 Jakob Unterwurzacher 2021-03-20T17:27:34+00:00 urn:sha1:692a79461a7b0f60625ecf8b1a136bc6595f1273 Currently fails like this: === RUN TestRmwRace doRead 0: corrupt block #0: cipher: message authentication failed -wpanic turns this warning into a panic: doRead 0: corrupt block #0: cipher: message authentication failed panic: -wpanic turns this warning into a panic: doRead 0: corrupt block #0: cipher: message authentication failed goroutine 1293 [running]: log.(*Logger).Panic(0xc00011c230, 0xc0003b17c8, 0x1, 0x1) log/log.go:224 +0xac github.com/rfjakob/gocryptfs/internal/tlog.(*toggledLogger).Printf(0xc00007a780, 0x55a821a766a1, 0x20, 0xc0003b19f0, 0x3, 0x3) github.com/rfjakob/gocryptfs/internal/tlog/log.go:78 +0x1ef github.com/rfjakob/gocryptfs/internal/fusefrontend.(*File).doRead(0xc0001ff420, 0x0, 0x0, 0x0, 0x0, 0x1000, 0x0, 0x1, 0xc000880000, 0x1020) github.com/rfjakob/gocryptfs/internal/fusefrontend/file.go:201 +0x8c9 github.com/rfjakob/gocryptfs/internal/fusefrontend.(*File).doWrite(0xc0001ff420, 0xc000248428, 0x10, 0x30, 0xff0, 0x3, 0x18) github.com/rfjakob/gocryptfs/internal/fusefrontend/file.go:291 +0xc9e github.com/rfjakob/gocryptfs/internal/fusefrontend.(*File).Write(0xc0001ff420, 0x55a821b306a0, 0xc000fbde90, 0xc000248428, 0x10, 0x30, 0xff0, 0x7f4a00000000, 0x0) github.com/rfjakob/gocryptfs/internal/fusefrontend/file.go:378 +0x25e github.com/hanwen/go-fuse/v2/fs.(*rawBridge).Write(0xc000168140, 0xc000096000, 0xc0002483d8, 0xc000248428, 0x10, 0x30, 0x55a821ad40e0) github.com/hanwen/go-fuse/v2@v2.0.4-0.20210125162859-8e0bbdb16cb7/fs/bridge.go:819 +0x26d github.com/hanwen/go-fuse/v2/fuse.doWrite(0xc000170160, 0xc000248240) github.com/hanwen/go-fuse/v2@v2.0.4-0.20210125162859-8e0bbdb16cb7/fuse/opcode.go:191 +0x6f github.com/hanwen/go-fuse/v2/fuse.(*Server).handleRequest(0xc000170160, 0xc000248240, 0xc000000000) github.com/hanwen/go-fuse/v2@v2.0.4-0.20210125162859-8e0bbdb16cb7/fuse/server.go:472 +0x2be github.com/hanwen/go-fuse/v2/fuse.(*Server).loop(0xc000170160, 0xc000cd4101) github.com/hanwen/go-fuse/v2@v2.0.4-0.20210125162859-8e0bbdb16cb7/fuse/server.go:445 +0x198 created by github.com/hanwen/go-fuse/v2/fuse.(*Server).readRequest github.com/hanwen/go-fuse/v2@v2.0.4-0.20210125162859-8e0bbdb16cb7/fuse/server.go:312 +0x41d matrix_test.go:354: Write failed 2021-03-20T09:33:34+00:00 Jakob Unterwurzacher 2021-03-20T09:33:34+00:00 urn:sha1:255a71c9179b9ad32587b20c41f81dc0b8cc3f44 Allows to drop a few Mkdir()s. 2021-03-12T18:25:25+00:00 Jakob Unterwurzacher 2021-03-12T18:25:25+00:00 urn:sha1:952d45ce84f63de963a1727e439e95883f9e65c1 Also fix incomplete uid restoration in TestSupplementaryGroups and replace syscall.Setregid and friends with unix.Setregid and friends. This test is added to check if have problems handling a full disk. The ticket https://github.com/rfjakob/gocryptfs/issues/550 states that the full disk was not where the backing gocryptfs filesystem was, but this has no effect on gocryptfs, so we test the harder case. 2021-03-07T16:22:29+00:00 Jakob Unterwurzacher 2021-03-07T16:22:29+00:00 urn:sha1:e2dc52a9657e530820b2d5b49ad7425b529029ce Hard link tracking was not correctly disabled since the migration to the go-fuse v2 api. Add a test to ensure it stays off. Fixes https://github.com/rfjakob/gocryptfs/issues/525 2021-02-07T19:01:16+00:00 Jakob Unterwurzacher 2021-02-07T19:01:16+00:00 urn:sha1:eaca820e876bfcdc67323eac6dd43ecc420968f2 Pass through system.posix_acl_access and system.posix_acl_default unencrypted to fix "cp -a" problems. "cp -a" uses "setxattr" even to set normal permissions, see https://www.spinics.net/lists/linux-nfs/msg63986.html . Fixes https://github.com/rfjakob/gocryptfs/issues/543 2021-02-07T19:00:33+00:00 Jakob Unterwurzacher 2021-02-07T19:00:33+00:00 urn:sha1:bb2484f1520102f4ab6c84400f9eef53d4cdd2ad The blob was truncated to 31 bytes.