gocryptfs/internal/syscallcompat, branch v1.5Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v1.52018-06-07T22:47:48+00:00darwin does not have PATH_MAX2018-06-07T22:47:48+00:00Jakob Unterwurzacher2018-06-07T22:47:48+00:00urn:sha1:bde7ba57b06eb46f8901454e12524a74a8c3b6e8
Define our own, with the value from Linux.
Fix the easy golint warnings2018-04-08T18:26:25+00:00Jakob Unterwurzacher2018-04-08T18:24:29+00:00urn:sha1:bcc8378a2c07476a43c1fe316b79590177ded3d3
Reported by https://goreportcard.com/report/github.com/rfjakob/gocryptfs
macos: tests: fix deleting of scratch dir2018-03-05T22:40:08+00:00Jakob Unterwurzacher2018-03-05T22:40:08+00:00urn:sha1:4732e33a9a39935ecc07dfb7e857cc05b6fc6045
macos rm does not understand --one-file-system,
and it cannot handle unreadable directories.
macos: fix second TestEmulateSymlinkat test failure2018-03-05T20:20:07+00:00Jakob Unterwurzacher2018-03-05T20:20:07+00:00urn:sha1:7db5395c5346a1b32656b27e504417779435edc8MacOS: don't test symlinks longer than 1000 bytes2018-02-28T19:40:08+00:00Jakob Unterwurzacher2018-02-28T19:40:08+00:00urn:sha1:c5243fc79e25cd589e78f47dafe0e8144885e6e4
The limit is much lower than on Linux.
https://github.com/rfjakob/gocryptfs/issues/213
MacOS: fix TestEmulateSymlinkat test failure2018-02-28T19:19:31+00:00Jakob Unterwurzacher2018-02-28T19:19:31+00:00urn:sha1:90f2fea7fba8cd2cab1c28471f955a99f91ca0ad
On MacOS, symlinks don't have their own permissions,
so don't check for them.
gccgo: skip emulateGetdents on linux2018-02-04T20:14:12+00:00Jakob Unterwurzacher2018-02-04T20:13:14+00:00urn:sha1:8151222ada4c687bfad7e2f35c73aacbbc24c6b5
The test is known to fail on gccgo
(https://github.com/rfjakob/gocryptfs/issues/201), but
getdents emulation is not used on linux, so let's skip
the test and ignore the failure.
Fix assignment error in Unix2syscall by converting Timespec into Nsec (#203)2018-02-03T12:42:49+00:00Felix Lechner2018-02-03T12:42:49+00:00urn:sha1:5b986288cf0139a612710de728e82192d1f63fa2
$ go.gcc build
# github.com/rfjakob/gocryptfs/internal/syscallcompat
internal/syscallcompat/unix2syscall_linux.go:32:13: error: incompatible types in assignment (cannot use type int64 as type syscall.Timespec_sec_t)
s.Atim.Sec = u.Atim.Sec
^gccgo: replace syscall.NAME_MAX with unix.NAME_MAX2018-02-01T22:50:11+00:00Jakob Unterwurzacher2018-02-01T22:46:02+00:00urn:sha1:9f8d0d8e5734e3771b52c8a8784ef5a76b0f9ca8
For some reason the syscall.NAME_MAX constant does not exist
on gccgo, and it does not hurt us to use unix.NAME_MAX instead.
https://github.com/rfjakob/gocryptfs/issues/201
syscallcompat: switch from syscall.Getdents to unix.Getdents2018-01-31T17:59:10+00:00Jakob Unterwurzacher2018-01-31T17:59:10+00:00urn:sha1:26ba8103bf2422493a01b57b8ee53aa9b1e867f7
On mips64le, syscall.Getdents() and struct syscall.Dirent do
not fit together, causing our Getdents implementation to
return garbage ( https://github.com/rfjakob/gocryptfs/issues/200
and https://github.com/golang/go/issues/23624 ).
Switch to unix.Getdents which does not have this problem -
the next Go release with the syscall package fixes is too
far away, and will take time to trickle into distros.