libgocryptfs/internal/fusefrontend
Jakob Unterwurzacher a602e798b1 fusefrontend: report an error if all files in a directory were invalid
Just presenting an empty directory means that the user does not know
that things went wrong unless he checks the syslog or tries to delete
the directory.

It would be nice to report the error even if only some files were
invalid. However, go-fuse does not allow returning the valid
directory entries AND an error.
2016-06-04 16:39:27 +02:00
..
args.go longnames part I: Create and OpenDir work with long filenames > 176 bytes 2016-02-06 22:54:14 +01:00
compat_darwin.go Move pathfs_frontend to internal/fusefrontend 2016-02-06 19:27:59 +01:00
compat_linux.go prelloc: warn and continue if fallocate(2) is not supported 2016-04-20 22:47:31 +02:00
file.go fusefrontend: replace unreliable "fd < 0" check 2016-05-30 09:36:06 +02:00
file_holes.go Move pathfs_frontend to internal/fusefrontend 2016-02-06 19:27:59 +01:00
fs.go fusefrontend: use sync.Once for one-time warnings 2016-05-29 22:50:03 +02:00
fs_dir.go fusefrontend: report an error if all files in a directory were invalid 2016-06-04 16:39:27 +02:00
names.go longnames part I: Create and OpenDir work with long filenames > 176 bytes 2016-02-06 22:54:14 +01:00
write_lock.go fusefrontend: simplify wlockMap 2016-05-29 22:40:05 +02:00