summaryrefslogtreecommitdiff
path: root/tests/example_filesystems/v0.9/gocryptfs.diriv
diff options
context:
space:
mode:
authorJakob Unterwurzacher2017-05-01 17:49:37 +0200
committerJakob Unterwurzacher2017-05-01 17:49:37 +0200
commit9ab11aa4d775f7c1242e8b044cc2f8957cc2c784 (patch)
treef4f302b3573dff151b2290d6f1a2d9436cd24e57 /tests/example_filesystems/v0.9/gocryptfs.diriv
parent514f515dd7196e26ca8df6886ac4a34e928e50dd (diff)
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.
Diffstat (limited to 'tests/example_filesystems/v0.9/gocryptfs.diriv')
0 files changed, 0 insertions, 0 deletions