Date: Fri, 11 Aug 2017 21:26:22 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 218101] [fuse] [request] support entry_timeout / attr_timeout Message-ID: <bug-218101-3630-UuhXKRlFpZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218101-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-218101-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218101 --- Comment #1 from Ben RUBSON <ben.rubson@gmail.com> --- Here is a test case for this request report : # Create a Fuse EncFS in reverse mode (will give an encrypted view of the p= lain folder) : plain=3D/tmp/encfs_test/plain ciphr=3D/tmp/encfs_test/ciphr mkdir -p $plain $ciphr encfs --extpass=3D"echo test" --standard $plain $ciphr --reverse # Update a file in the plain folder while [ 1 ]; do echo >>$plain/file ; sleep 0.5; done # Monitor the files in the encrypted view : while [ 1 ]; do clear; stat $ciphr/*; sleep 0.5; done As you can see, the timestamps correctly get updated, but not the sizes. It's then dangerous because if you open the encrypted file (using dd for example, dd if=3D$ciphr/... of=3D/dev/null), it will then be truncated (!) to the size being displayed by stat, whereas it was in reality much bigger, as its plain version was growing. I found fuse sysctls, some are cache related, but no benefit. Adding "-o attr_timeout=3D0 -o entry_timeout=3D0" to the encfs command in Linux makes this to work. Thank you ! Ben --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218101-3630-UuhXKRlFpZ>