Jakob Unterwurzacher 9ab11aa4d7 fusefrontend: drop writeOnly flag ... We do not have to track the writeOnly status because the kernel will not forward read requests on a write-only FD to us anyway. I have verified this behavoir manually on a 4.10.8 kernel and also added a testcase.		2017-05-01 17:49:37 +02:00
..
cli	Check for trailing garbage after the password	2017-02-12 17:59:09 +01:00
defaults	fusefrontend: drop writeOnly flag	2017-05-01 17:49:37 +02:00
example_filesystems	cli: enable "-raw64" by default	2017-03-07 20:56:50 +01:00
hkdf_sanity	tests: add hkdf_sanity tests with broken example filesystem	2017-03-18 16:48:58 +01:00
matrix	Drop Go 1.4 compatability code everywhere	2017-03-05 17:44:14 +01:00
plaintextnames	Fix misspellings	2016-10-24 19:18:13 +02:00
reverse	tests: reverse: don't run tests that ignore "-plaintextnames" twice	2017-03-07 20:53:58 +01:00
stress_tests	Get rid of remaining $GOPATH dependencies	2017-02-20 21:26:42 +01:00
test_helpers	tests: get rid of syscall.PathMax	2017-02-16 18:47:04 +01:00
canonical-benchmarks.bash	benchmark: add md5sum read performance benchmark	2017-03-18 16:23:33 +01:00
dl-linux-tarball.bash	tests: OSX compat: use OSX-style "stat -f"	2017-02-16 19:10:36 +01:00
fuse-unmount.bash	OSX compat: replace fusermount calls with fuse-unmount.bash	2017-02-15 23:02:01 +01:00
maxlen.bash	maxlen.bash: result was 1 too high	2016-10-04 10:26:22 +02:00