Al Viro wrote:
On Wed, Nov 02, 2016 at 11:53:40PM +0100, Jose Lopes wrote:
Syscall 'ftruncate' makes the 'file' struct available to filesystem
handlers. This makes it possible, e.g., for filesystems, such as,
FUSE, to access the file handle associated with the file descriptor
that was passed to 'ftruncate'. In the specific case of FUSE, this
also makes it possible for (userspace) FUSE-based filesystems to
distinguish between calls to 'truncate' and 'ftruncate'.
Why FUSE is such a precious snowflake that it needs to make that distinction,
unlike all other filesystems?
For fuse file system which delegate the permission checks
to user space (and have to do so because of cacheing
issues), the write permission has to be checked for
truncate(), and not checked for ftruncate() : the file
may have been opened for writing and then its permissions
set to read-only before the ftruncate() is requested.
The user space file system can check current permissions,
not the ones which were set when the file was opened.
Jean-Pierre
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
