gocryptfs/tests/stress_tests, branch v2.3.0 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.3.0 2021-09-01T08:22:01+00:00 *: trim trailing whitespace 2021-09-01T08:22:01+00:00 a1346054 2021-08-31T17:05:38+00:00 urn:sha1:7c2255be9027551a1df54b3cb58ea9493857d391 shell scripts: fix shellcheck warnings 2021-09-01T08:22:01+00:00 a1346054 2021-08-31T17:01:47+00:00 urn:sha1:c63f7e9f64ee394b3311edb7f36f56fd786d145a fsstress-gocryptfs: fuse-xfstests now lives in /opt 2021-08-26T05:46:28+00:00 Jakob Unterwurzacher 2021-08-26T05:46:28+00:00 urn:sha1:7b25ff39c81aea559e7a2fd3a5f6143e95521ce2 fuse-xfstests should be installed to /opt now to make the terminal output independent of the user name (as done in https://github.com/rfjakob/fuse-xfstests/wiki/results_2021-06-02 ) tests: fsstress-gocryptfs.bash: log timestamp for each iteration 2020-10-03T22:12:46+00:00 Jakob Unterwurzacher 2020-10-03T20:08:52+00:00 urn:sha1:754c48387038f78ac653bcc7e97582e1491cfbd9 tests: fsstress-gocryptfs.bash: add DEBUG option 2020-10-03T22:12:25+00:00 Jakob Unterwurzacher 2020-10-03T12:21:21+00:00 urn:sha1:66449bf56b22d2f6b6309649b4c4819217c1cee5 Also add a wrapper script, fsstress.collect-crashes.sh, to collect the debug output. https://github.com/hanwen/go-fuse/issues/372 fsstress-gocryptfs.bash: don't hang if TMPDIR ends in / 2020-10-03T12:23:37+00:00 Jakob Unterwurzacher 2020-09-18T16:39:31+00:00 urn:sha1:3c5a80c27ba096b6938caf9549227620fa522af4 We would hang like this ./fsstress-loopback.bash Recompile go-fuse loopback: v2.0.3-7-g0b6cbc5 Waiting for mount: xxxxxxxx^C if TMPDIR has a trailing /. The reason is that the paths in /proc/self/mounts are normalized, while TMPDIR may not be. fsstress-gocryptfs.bash: print loopback version & mount path 2020-09-18T16:31:22+00:00 Jakob Unterwurzacher 2020-09-18T11:27:55+00:00 urn:sha1:27c92f63be68ddb2cbdf35d38a623d3d5d24c2eb To make the used go-fuse version clear in logs, print it on startup, similar to what we do with gocryptfs. stress_tests/fsstress-gocryptfs.bash: use rm -Rf for cleanup 2020-09-13T12:14:23+00:00 Jakob Unterwurzacher 2020-09-13T12:09:38+00:00 urn:sha1:af7386713c33a476f6094d0c53a518a2c6b2c015 Apparently, kernel 5.8 now allows unprivileged "mknod /tmp/x c 0 0": vfs: allow unprivileged whiteout creation https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.8.9&id=a3c751a50fe6bbe50eb7622a14b18b361804ee0c which is why rm throws a new prompt: rm: remove write-protected character special file '...'? Use rm -Rf to suppress that. stress_tests: run pingpong.bash at nice level 19 2020-07-26T18:01:30+00:00 Jakob Unterwurzacher 2020-07-26T17:55:17+00:00 urn:sha1:9e0b07ec995c5320a2ba227a71da9a8d9fe2581b Like extractloop.bash. tests: fsstress: clean up leftover mounts on startup 2019-11-10T21:06:40+00:00 Jakob Unterwurzacher 2019-11-10T21:06:40+00:00 urn:sha1:f7ddae24eda373e8680ffb9d4b7ef74dea36f60f Broken mounts may accumulate when the fs crashes.