hardcoresushi/libgocryptfs
1
0
Fork 0
Code Issues Pull Requests Releases Activity
778c955eea
libgocryptfs/internal/fusefrontend_reverse
History
Jakob Unterwurzacher 778c955eea fusefrontend_reverse: switch to stable inode numbers 
The volatile inode numbers that we used before cause "find" to complain and error out.
Virtual inode numbers are derived from their parent file inode number by adding 10^19,
which is hopefully large enough no never cause problems in practice.

If the backing directory contains inode numbers higher than that, stat() on these files
will return EOVERFLOW.

Example directory lising after this change:

  $ ls -i
               926473 gocryptfs.conf
  1000000000000926466 gocryptfs.diriv
               944878 gocryptfs.longname.hmZojMqC6ns47eyVxLlH2ailKjN9bxfosi3C-FR8mjA
  1000000000000944878 gocryptfs.longname.hmZojMqC6ns47eyVxLlH2ailKjN9bxfosi3C-FR8mjA.name
               934408 Tdfbf02CKsTaGVYnAsSypA
2017-04-01 17:19:15 +02:00
..
ctlsock_interface.go fusefrontend_reverse: convert fmt.Printf calls to tlog 2017-04-01 15:49:53 +02:00
reverse_longnames.go fusefrontend_reverse: add comment to newVirtualFile 2017-04-01 14:17:54 +02:00
rfile.go fusefrontend_reverse: convert fmt.Printf calls to tlog 2017-04-01 15:49:53 +02:00
rfs.go fusefrontend_reverse: switch to stable inode numbers 2017-04-01 17:19:15 +02:00
rpath_cache.go fusefrontend_reverse: convert fmt.Printf calls to tlog 2017-04-01 15:49:53 +02:00
rpath.go fusefrontend_reverse: switch to stable inode numbers 2017-04-01 17:19:15 +02:00
virtualfile.go fusefrontend_reverse: switch to stable inode numbers 2017-04-01 17:19:15 +02:00