gocryptfs/tests, branch v2.5.3Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v2.5.32025-04-05T09:46:07+00:00tests: fsck: generate evil files with "\r" and "\n" on the fly2025-04-05T09:46:07+00:00Jakob Unterwurzacher2025-04-05T09:31:14+00:00urn:sha1:c8055829c311ecaf532fd171f3a5d104f873272d
Because if we have them in git, we get this:
$ go install github.com/rfjakob/gocryptfs/v2@latest
go: downloading github.com/rfjakob/gocryptfs/v2 v2.5.2
go: github.com/rfjakob/gocryptfs/v2@latest: create zip: tests/fsck/malleable_base64/27AG8t-XZH7G9ou2OSD_z
g: malformed file path "tests/fsck/malleable_base64/27AG8t-XZH7G9ou2OSD_z\ng": invalid char '\n'
g: malformed file path "tests/fsck/malleable_base64/27AG8t-XZH7G9ou2OSD_z\rg": invalid char '\r'
Fixes: https://github.com/rfjakob/gocryptfs/issues/904
Relates-to: https://github.com/golang/go/issues/28001
tests/root_test: use our own Setgroups/Setregid/Setreuid wrappers2025-02-26T20:56:25+00:00Jakob Unterwurzacher2025-02-26T20:56:25+00:00urn:sha1:0024b056d668290e5105527e8ff0a3b23a3a70c8tests/root_test: add TestConcurrentUserOps and TestAsUserSleep2025-02-23T21:34:56+00:00Jakob Unterwurzacher2025-02-23T21:29:17+00:00urn:sha1:178f570d4076ee9be408c9eb5e50502275a180c6
Both work with
golang.org/x/sys v0.0.0-20220520151302-bc2c85ada10a
but break with
golang.org/x/sys v0.30.0
https://github.com/rfjakob/gocryptfs/issues/893
https://github.com/rfjakob/gocryptfs/issues/892
tests: root_test: add TestMain2025-02-17T20:37:41+00:00Jakob Unterwurzacher2025-02-17T20:37:41+00:00urn:sha1:3c82930d4ad22b5be2f644346018a0550dd66aa8
I will add more tests for https://github.com/rfjakob/gocryptfs/issues/893
soon, these will also use DefaultPlainDir.
tests: add issue893.sh, a reproducer for #893 "mariadb crashing since 2.5.0"2025-01-23T21:17:51+00:00Jakob Unterwurzacher2025-01-23T21:16:29+00:00urn:sha1:00d4d91048fd6ae3017ced1f3937357c14e8e548
https://github.com/rfjakob/gocryptfs/issues/893
tests: reverse: TestMtimePlus10: fix darwin build2025-01-18T13:46:14+00:00Jakob Unterwurzacher2025-01-18T13:46:14+00:00urn:sha1:a0105e65cde9f4643a896770a9629da644613a8a
Darwin does not have Stat_t.mtim:
+ go test -c -tags without_openssl -o /dev/null github.com/rfjakob/gocryptfs/v2/tests/reverse
Error: tests/reverse/correctness_test.go:407:15: name_stat.Mtim undefined (type syscall.Stat_t has no field or method Mtim)
Error: tests/reverse/correctness_test.go:407:37: long_stat.Mtim undefined (type syscall.Stat_t has no field or method Mtim)
Error: tests/reverse/correctness_test.go:410:15: name_stat.Ctim undefined (type syscall.Stat_t has no field or method Ctim)
Error: tests/reverse/correctness_test.go:410:37: long_stat.Ctim undefined (type syscall.Stat_t has no field or method Ctim)
Error: tests/reverse/correctness_test.go:424:16: diriv_stat.Mtim undefined (type syscall.Stat_t has no field or method Mtim)
Error: tests/reverse/correctness_test.go:424:42: workdirA_stat.Mtim undefined (type syscall.Stat_t has no field or method Mtim)
Error: tests/reverse/correctness_test.go:427:16: diriv_stat.Ctim undefined (type syscall.Stat_t has no field or method Ctim)
Error: tests/reverse/correctness_test.go:427:42: workdirA_stat.Ctim undefined (type syscall.Stat_t has no field or method Ctim)
Switch to os.Stat.
tests: skip TestFileHoleCopy for now2025-01-18T13:27:27+00:00Jakob Unterwurzacher2025-01-18T13:27:27+00:00urn:sha1:38936cba4e319525875feaa5d44b85819692e056
This problem potentially causes extra disk usage for sparse files
but is otherwise harmless.
Skip the test for now.
reverse: advance mtime & ctime for virtual files by 10 seconds2025-01-18T13:13:52+00:00Jakob Unterwurzacher2025-01-18T13:11:51+00:00urn:sha1:9eb47cf546d7e2499eab210d70050ef78087475a
With inode number reuse and hard links, we could have returned
wrong data for gocryptfs.diriv and gocryptfs.xyz.longname files, respectively
(https://github.com/rfjakob/gocryptfs/issues/802).
Now that this is fixed, ensure that rsync and similar tools pick up the new
correct files by advancing mtime and ctime by 10 seconds, which should be more
than any filesytems' timestamp granularity (FAT32 has 2 seconds).
tests: reverse: factor out newWorkdir2025-01-18T13:13:52+00:00Jakob Unterwurzacher2025-01-18T12:56:51+00:00urn:sha1:c19f986ba09e675a5139b12bcf2687495f2533dd
Will be used in a new test in the next commit.
tests: ignore pidfd in fd leak test2024-12-04T18:51:33+00:00Jakob Unterwurzacher2024-12-04T18:51:33+00:00urn:sha1:9529f5da0f608c7dbc7b7be095d89039d6a3a5b6
This is not a real leak:
fd leak in test process? before, after:
[0r=/dev/null 3r=/proc/940141/fd 5rw=anon_inode:[eventfd] (filtered: pipe:[2454797], pipe:[2454797], anon_inode:[eventpoll])]
[0r=/dev/null 3r=/proc/940141/fd 5rw=anon_inode:[eventfd] 12rw=anon_inode:[pidfd] (filtered: pipe:[2454797], pipe:[2454797], anon_inode:[eventpoll], pipe:[2460158])]
Ignore pidfd.