e36a0ebf18
At the moment, it does two things: 1. Disable stat() caching so changes to the backing storage show up immediately. 2. Disable hard link tracking, as the inode numbers on the backing storage are not stable when files are deleted and re-created behind our back. This would otherwise produce strange "file does not exist" and other errors. Mitigates https://github.com/rfjakob/gocryptfs/issues/156 |
||
---|---|---|
.. | ||
CLI_ABI.md | ||
duplicate-inodes.txt | ||
file-format.md | ||
gocryptfs-logo.png | ||
MANPAGE-render.bash | ||
MANPAGE.md | ||
openssl-gcm.md | ||
performance.txt | ||
SECURITY.md | ||
XFSTESTS.md |