From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vyacheslav Dubeyko Subject: Re: [6/8] Rich ACLs (continued, drive through this time) Date: Mon, 08 Apr 2013 15:12:29 +0400 Message-ID: <1365419549.2673.30.camel@slavad-ubuntu> References: <516299A5.8030109@panasas.com> <51629F0E.7020301@panasas.com> Reply-To: slava@dubeyko.com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Steven Whitehouse , Steve Dickson , Jeff Layton , lsf-pc@lists.linux-foundation.org, linux-fsdevel , Ganesha NFS List , Frank S Filz , "J. Bruce Fields" , "Lieb, Jim" , Venkateswararao Jujjuri , DENIEL Philippe To: Boaz Harrosh Return-path: Received: from oproxy7-pub.bluehost.com ([67.222.55.9]:46047 "HELO oproxy7-pub.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751635Ab3DHLMr (ORCPT ); Mon, 8 Apr 2013 07:12:47 -0400 In-Reply-To: <51629F0E.7020301@panasas.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi Boaz, On Mon, 2013-04-08 at 13:42 +0300, Boaz Harrosh wrote: > From the top of my head please correct me where I'm wrong. > > Anish Kumar from IBM has posted a patchset to support rich ACLs at Filesystems of interest > Specially also by the NFS client FS, and through the KNFSD by the exported FSs of interest. > > His approach was to have both the POSIX-ACLs and the RICH-ACLs, co exist at the VFS and FS > layer, and to interact nicely together. But a supporting FS needs to support two APIs and > do its own code refactoring at the bottom. > > What the VFS community wanted to see is that all FS APIs change to the bigger RICH-ACLs > API, and the translation from rich to POSIX is done at the generic VFS layer, thoughts > doing the refactoring once at the VFS. > Yes, RICH-ACLs is important topic. HFS+ uses NFSv4 ACLs model but with own peculiarities. I published not so recently path set with implementation of ACLs support in HFS+ driver. I used as a basis mapping code (NFSv4 <-> POSIX ACLs) that it was implemented in nfsd. And J. Bruce Fields makes remark about necessity to generalize mapping code with purpose of sharing it between drivers. So, I am working on generalization mapping code (NFSv4 <-> POSIX ACLs) for using it in HFS+ driver. I hope that I'll finish this work soon. But, anyway, the RICH-ACLs scheme is more natural for HFS+. With the best regards, Vyacheslav Dubeyko. > Anish pressed between his IBM obligations and the huge amount of coding it will take > to convert all FSs, has put the project on a back burner, and we have not seen any > farther changes from him. > > JV Please find and post a git tree with the latest code. And if there are some > documentation post them here. Please also try to find the original ML thread that > is captured above. > > [Proposition] > > There are more interested parties then Anish in this matter. I know for a fact that IBM, > Panasas RedHat, and any NFS and CIFS community member would like to see this work done. > I propose that we get a status update, on what's there now. Talk about a strategy for > an incremental but complete Kernel transformation, and finally submission. And I think > All parties above should invest in time and resources together to drive this through. I would > like to see all this done under Anish's guide if possible. > > [JV what is Anish's email ?] > > [user-mode API] > And we will need a good local API for get/set of rich ACLs, currently they are interfaced > through either a Windows CIFS client or through some NFS4 test applications. There should > be an API that can be used both at the local FS as well as via the NFS-client. > (And the new readdir-plus should give us a flag if there are ACLs present at an entry) > > Thanks > Boaz > > -- > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html