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
..
args.go	Add -forcedecode	2017-04-23 23:11:56 +02:00
ctlsock_interface.go	ctlsock: better error message for forward mode path decryption	2017-01-29 18:55:52 +01:00
file_allocate_truncate.go	fusefronted, openfiletable: move the open file table to its own package	2017-05-01 17:26:50 +02:00
file_holes.go	fusefrontend: truncateGrowFile: avoid createHeader() call	2017-03-12 21:06:59 +01:00
file.go	fusefrontend: drop writeOnly flag	2017-05-01 17:49:37 +02:00
fs_dir.go	fusefrontend: use Lchown when preserving owner	2016-11-28 22:46:04 +01:00
fs.go	fusefrontend: drop writeOnly flag	2017-05-01 17:49:37 +02:00
names.go	nametransform: delete unused function DecryptPathDirIV	2016-09-25 18:56:23 +02:00