Return-Path: Date: Wed, 2 Sep 2009 12:42:43 -0400 To: "Aneesh Kumar K.V" Subject: Re: POSIX ACL support for NFSV4 (using sideband protocol) Message-ID: <20090902164243.GA17126@fieldses.org> References: <1251894268-1555-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com> In-Reply-To: <1251894268-1555-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com> From: "J. Bruce Fields" Cc: linux-nfs@vger.kernel.org, trond.myklebust@netapp.com, nfsv4@linux-nfs.org, sfrench@us.ibm.com, agruen@suse.de List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: nfsv4-bounces@linux-nfs.org Errors-To: nfsv4-bounces@linux-nfs.org MIME-Version: 1.0 List-ID: On Wed, Sep 02, 2009 at 05:54:20PM +0530, Aneesh Kumar K.V wrote: > This patch series implement POSIX ACL support for NFSV4 clients > using sideband protocol. What motivates this? Who exactly wants this and why? What would be the advantages compared to other options, such as: - native v4 support in filesystems, or - improved client-side acl tools that provided a user interface for v4 acls closer to that for v3 acls, or - a v4.x extension to add support to the main protocol? Is there interest in implementing this on any OS other than linux, or would this be a linux-only extension for the forseeable future? What sideband protocol exactly? If it's exactly the same protocol as the one used with v3, there must be some slight mismatches: e.g. v4 filehandles are allowed to be longer. How do you deal with these? --b. > The ACL support can be disabled/enabled > using -o noacl/-o acl mount option. The feature enables to > view and modify POSIX acls from NFSv4 client. _______________________________________________ NFSv4 mailing list NFSv4@linux-nfs.org http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4