gocryptfs/internal/fusefrontend/fs_dir.go, branch xattr_user_bufferMirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer2020-07-26T16:35:12+00:00v2api: delete (most) fusefrontend v1 files2020-07-26T16:35:12+00:00Jakob Unterwurzacher2020-07-26T16:35:12+00:00urn:sha1:777b95f82ffea8a25b95089343b07b29378110da
All the functionality in these files has been reimplemented
for the v2 api. Drop the old files.
v2api: implement Mkdir2020-06-21T11:46:08+00:00Jakob Unterwurzacher2020-06-21T11:46:08+00:00urn:sha1:192a29075a7a567931959c2b4c8e4a9513742eeefusefrontend: don't clear dircache on Mkdir2020-05-24T13:30:14+00:00Jakob Unterwurzacher2020-05-24T12:57:30+00:00urn:sha1:2a9b99a0ef8d1eb8b067374462f31a19a098ef64
Mkdir can not cause existing entries in the cache to go
stale. So don't clear it. Benchmark results:
sshfs-benchmark.bash: sshfs gocryptfs-on-sshfs
git init 1.65 8.74
rsync 6.09 17.54
Update go-fuse import path to github.com/hanwen/go-fuse/v22020-05-17T12:23:47+00:00Jakob Unterwurzacher2020-05-17T12:18:23+00:00urn:sha1:ec74d1d2f4217a9a337d1db9902f32ae2aecaf33
We need
https://github.com/hanwen/go-fuse/commit/fd7328faf9fdf75709f7ba7df7072aaf4eeb18b3
to fix a crash reported in https://github.com/rfjakob/gocryptfs/issues/430 :
2019/10/30 17:14:16 Unknown opcode 2016
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x508d38]
This patch is only in the v2.x.x branch. Upgrade to v2, as the
old API is also supported there.
Running
git grep hanwen/go-fuse | grep -v hanwen/go-fuse/v2
to check for forgotten references comes back clean.
fusefrontend: warn about missing diriv2019-11-03T19:38:15+00:00Jakob Unterwurzacher2019-11-03T19:38:15+00:00urn:sha1:e4148028af1f113bfdec00f3c577ef2d428a6aad
The comment is outdated, at this point, we should
really not get any errors from ReadDirIVAt.
The change is best seen when running the fsck tests. Before:
fsck: error opening dir "missing_diriv": 2=no such file or directory
After:
OpenDir "K2m0E6qzIfoLkVZJanoUiQ": could not read gocryptfs.diriv: no such file or directory
fsck: error opening dir "missing_diriv": 5=input/output error
See https://github.com/rfjakob/gocryptfs/issues/403 , where
the extra info would have been helpful.
fusefrontend: don't return EIO on directory with corrupt file names2019-11-03T19:12:05+00:00Jakob Unterwurzacher2019-11-03T19:12:05+00:00urn:sha1:93939961f57e881f2b82293aa8749ea6f1ba6180
This was meant as a way to inform the user that
something is very wrong, however, users are hitting
the condition on MacOS due to ".DS_Store" files, and
also on NFS due to ".nfsXXX" files.
Drop the whole thing as it seems to cause more pain
than gain.
Fixes https://github.com/rfjakob/gocryptfs/issues/431
fusefrontend: get rid of last hardcoded "gocryptfs.diriv" instances2019-04-09T18:51:33+00:00Jakob Unterwurzacher2019-04-09T18:51:33+00:00urn:sha1:7d81494a649f3f871bfeb4bb129cbfa738fbef67
Makes it easier to change the name (as some people want to):
https://github.com/rfjakob/gocryptfs/issues/37
fusefrontend: ensure directories without W or X perms can be deleted2019-01-20T13:29:28+00:00Jakob Unterwurzacher2019-01-20T13:29:28+00:00urn:sha1:962c52364415496b64a42b49fe5f90d593dc09f7
This fixed the "Permission denied" bug, but still has the problem that
the directory may be replaced behind our back. Mitigated by the fact
that we skip the workaround when running as root with -allow_other.
https://github.com/rfjakob/gocryptfs/issues/354
syscallcompat: rework Fchmodat to FchmodatNofollow2019-01-14T20:54:16+00:00Jakob Unterwurzacher2019-01-14T20:54:16+00:00urn:sha1:a7d59032d3790e117a48be6be1fb3a968266093b
We never want Fchmodat to follow symlinks, so follow what
Qemu does, and call our function FchmodatNofollow.
fusefrontend: Preserve SUID/SGID/sticky-bits in openWriteOnlyFile and Rmdir.2019-01-12T20:24:50+00:00Sebastian Lackner2019-01-12T20:24:48+00:00urn:sha1:99e8b6d288b1551947faec669b6af65331441471
Fixes https://github.com/rfjakob/gocryptfs/issues/336 and
https://github.com/rfjakob/gocryptfs/issues/337.