gocryptfs/tests/test_helpers, branch v1.6Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v1.62018-08-11T20:37:22+00:00tests: VerifyExistence: panic on inconsistent results2018-08-11T20:37:22+00:00Jakob Unterwurzacher2018-08-11T20:37:22+00:00urn:sha1:06f1ea951b03b4a0e8f6090c6657b8e0238da271
In the past we did not check whether all methods of checking
the file return the same result. We should.
main: accept -dev, -nodev, -suid, -nosuid, -exec, -noexec2018-06-07T20:50:30+00:00Jakob Unterwurzacher2018-06-07T20:50:30+00:00urn:sha1:53d6a9999dd0e4c31636d16179f284fff35a35d9
When mounted via /etc/fstab like this,
/a /b fuse.gocryptfs default 0 0
we always get extra options passed. As reported by @mahkoh
at https://github.com/rfjakob/gocryptfs/pull/233 :
mount passes `-o noexec` if `-o user` is set and `-o exec` is not set.
If both `-o user` and `-o exec` are set, it passes `-o exec`.
Make these options work, and in addtion, also make -suid and -rw
work the same way.
Reported-by: @mahkoh
tests: helpers: fix a few error reports2018-04-27T18:19:51+00:00Jakob Unterwurzacher2018-04-27T18:19:51+00:00urn:sha1:996d2f141b2c4f0cb9b8fbf66d06a2fb6e8cbaef
These were using stale err values.
Fix the easy golint warnings2018-04-08T18:26:25+00:00Jakob Unterwurzacher2018-04-08T18:24:29+00:00urn:sha1:bcc8378a2c07476a43c1fe316b79590177ded3d3
Reported by https://goreportcard.com/report/github.com/rfjakob/gocryptfs
tests: retry umount2018-04-08T18:09:05+00:00Jakob Unterwurzacher2018-04-08T18:09:05+00:00urn:sha1:cab0cda449c831d1d5bb9b75452428c186079799
Gnome may still have files open causing spurious test
failures.
tests: matrix: check for fd leaks2018-04-07T13:24:00+00:00Jakob Unterwurzacher2018-04-07T13:21:05+00:00urn:sha1:22031d7e531985e9e94d694e74fb00da99de72a5
And fix two in test_helpers.Mount().
Leftover fds can cause an unmount failure like this later:
fusermount: failed to unmount /tmp/gocryptfs-test-parent/873632270/default-plain: Device or resource busy
so try to catch them early.
fsck: add initial implementation2018-04-02T14:38:18+00:00Jakob Unterwurzacher2018-04-01T19:23:32+00:00urn:sha1:f28d85fad599ffaef9a8e1f353911c81a6605d2f
Most corruption cases except xattr should be covered.
With test filesystem.
The output is still pretty ugly. xattr support will
be added in the next commits.
test_helpers: add SwitchTestParentDir2018-03-24T20:40:11+00:00Jakob Unterwurzacher2018-03-24T20:37:41+00:00urn:sha1:f20974c4dad913a07ce5808005fe07084f87c95f
SwitchTestParentDir changes testParentDir. This is used when you want
to perform tests on a special filesystem. For example, the xattr tests
cannot run on tmpfs and use /var/tmp instead of /tmp.
tests: drop "-z" from fusermount to catch forgotten fds2018-03-06T20:28:09+00:00Jakob Unterwurzacher2018-03-06T20:22:01+00:00urn:sha1:98f735ff6e05ef71753f1c2fa60c30b195b02d3d
macos does not have lazy unmount, so let's not use it
on linux either.
If the unmount fails, run "lsof" to find the open file.
Also fix the first bug we found this way.
test_helpers: add missing newline2018-03-05T22:06:27+00:00Jakob Unterwurzacher2018-03-05T22:06:27+00:00urn:sha1:35192abb57636a8c4d6a6419aa6fd43f04ac2385