gocryptfs/pathfs_frontend/write_lock.go, branch xattr_user_bufferMirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer2016-02-06T18:27:59+00:00Move pathfs_frontend to internal/fusefrontend2016-02-06T18:27:59+00:00Jakob Unterwurzacher2016-02-06T18:27:59+00:00urn:sha1:9078a77850dd680bfa938d9ed7c83600a60c0e7b
"git status" for reference:
renamed: pathfs_frontend/args.go -> internal/fusefrontend/args.go
renamed: pathfs_frontend/compat_darwin.go -> internal/fusefrontend/compat_darwin.go
renamed: pathfs_frontend/compat_linux.go -> internal/fusefrontend/compat_linux.go
renamed: pathfs_frontend/file.go -> internal/fusefrontend/file.go
renamed: pathfs_frontend/file_holes.go -> internal/fusefrontend/file_holes.go
renamed: pathfs_frontend/fs.go -> internal/fusefrontend/fs.go
renamed: pathfs_frontend/fs_dir.go -> internal/fusefrontend/fs_dir.go
renamed: pathfs_frontend/names.go -> internal/fusefrontend/names.go
renamed: pathfs_frontend/write_lock.go -> internal/fusefrontend/write_lock.go
modified: main.go
Add per-inode write mutex2016-01-24T12:08:08+00:00Jakob Unterwurzacher2016-01-24T12:08:08+00:00urn:sha1:2f32114bd356c2124d75fb1879ff230fc1f0ca1b
At the moment, FUSE writes to a single file are serialized by the kernel.
However, it is unclear if this is guaranteed behaviour or may change
in the future.
This patch adds our own per-inode write lock to rule out races regardless
of kernel behavoir.