From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zeniv.linux.org.uk ([195.92.253.2]:47266 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750749AbcKCA7f (ORCPT ); Wed, 2 Nov 2016 20:59:35 -0400 Date: Thu, 3 Nov 2016 00:59:31 +0000 From: Al Viro To: Jose Lopes Cc: linux-fsdevel@vger.kernel.org, fuse-devel@lists.sourceforge.net Subject: Re: [PATCH] Make file struct available to fchmod FS handlers. Message-ID: <20161103005931.GB19539@ZenIV.linux.org.uk> References: <20161102225340.11613-1-jabolopes@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161102225340.11613-1-jabolopes@gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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? > In a future patch, make a similar change to the 'fchown' and > 'futimens' syscalls. I'm thucking frilled... NAK, unless you can give a better reason than "what if somebody would want that piece of information?".