Sebastian Lackner 9f56b33e0c fusefrontend: Fix longname handling for renames with existing target ... Fixes https://github.com/rfjakob/gocryptfs/issues/170 Steps to reproduce the problem: * Create a regular forward mount point * Create a file with a shortname and one with a long filename * Try to run 'mv <shortname> <longname>' This should actually work and replace the existing file, but instead it fails with: mv: cannot move '<shortname>' to '<longname>': File exists The problem is the creation of the .name file. If the target already exists we can safely ignore the EEXIST error and just keep the existing .name file.		2017-11-25 16:19:09 +01:00
..
dirivcache	dirivcache: add better function comments + a sanity check on Store()	2017-09-03 13:53:50 +02:00
diriv.go	nametransform: extend diriv cache to 100 entries	2017-08-09 22:00:53 +02:00
longnames_test.go	longnames: fix fsstress failure, use dirfd	2016-04-10 21:31:08 +02:00
longnames.go	fusefrontend: Fix longname handling for renames with existing target	2017-11-25 16:19:09 +01:00
names_test.go	nametransform: harden name decryption against invalid input	2017-05-23 21:26:38 +02:00
names.go	nametransform: Return error if decrypted name is '.' or '..'	2017-11-22 23:42:08 +01:00
pad16.go	nametransform: harden name decryption against invalid input	2017-05-23 21:26:38 +02:00