gocryptfs - Mirror of gocryptfs source code on Github

Age	Commit message (Collapse)	Author
2016-05-30	fusefrontend: replace unreliable "fd < 0" check	Jakob Unterwurzacher
	... with the "released" boolean. For some reason, the "f.fd.Fd() < 0" check did not work reliably, leading to nil pointer panics on the following wlock.lock(). The problem was discovered during fsstress testing and is unlikely to happen in normal operations. With this change, we passed 1700+ fsstress iterations.
2016-05-29	fusefrontend: use sync.Once for one-time warnings	Jakob Unterwurzacher
	Using a simple boolean was racy (which was harmless in this case) and non-idomatic.
2016-05-29	fusefronted: check Fstat return value on file create	Jakob Unterwurzacher
	The Fstat call should never fail, but still, if it does return an error it should be handled properly.
2016-05-29	fusefrontend: simplify wlockMap	Jakob Unterwurzacher
	mapMutex can be anonymous and using an RWMutex is overkill because the lock protects very short sections.
2016-05-29	fusefrontend: remove unused "forgotten" variable	Jakob Unterwurzacher
	The functionality has long been replaced by the fd < 0 check.
2016-05-12	Encrypt path in statfs() calls	David Gnedt
	Paths in statfs() calls were not encrypted resulting in an Function not implemented error, when the unencrypted path didn't exist in the underlying (encrypted) filesystem. $ df plain/existingdir df: ‘plain/existingdir’: Function not implemented
2016-05-08	fusefrontend: fix panic due to concurrently unregistered wlock	Jakob Unterwurzacher
	Commit 730291feab properly freed wlock when the file descriptor is closed. However, concurrently running Write and Truncates may still want to lock it. Check if the fd has been closed first.
2016-05-05	fusefrontend: fix wlock memory leak	Jakob Unterwurzacher
	The write lock was not freed on release, causing a slow memory leak. This was noticed by running extractloop.bash for 10 hours.
2016-04-20	prelloc: warn and continue if fallocate(2) is not supported	Jakob Unterwurzacher
	This makes gocryptfs work at all on ZFS. See https://github.com/rfjakob/gocryptfs/issues/22 .
2016-04-10	Fix "go tool vet -shadow=true" warnings	Jakob Unterwurzacher
	Among those one real bug.
2016-04-10	longnames: fix fsstress failure, use dirfd	Jakob Unterwurzacher
	Using dirfd-relative operations allows safe lockless handling of the ".name" files.
2016-04-10	longnames: use symbolic constants instead of naked ints	Jakob Unterwurzacher

2016-02-07	longnames part II: Rename, Unlink, Rmdir, Mknod, Mkdir + testsv0.9-rc1	Jakob Unterwurzacher

2016-02-07	Move OpenDir to fs_dir.go	Jakob Unterwurzacher

2016-02-06	longnames part I: Create and OpenDir work with long filenames > 176 bytes	Jakob Unterwurzacher
	Todo: Rename, Unlink, Rmdir, Mknod, Mkdir
2016-02-06	Run go fmt	Jakob Unterwurzacher

2016-02-06	Fix tests - were broken by the refactoring	Jakob Unterwurzacher

2016-02-06	Move pathfs_frontend to internal/fusefrontend	Jakob Unterwurzacher
	"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