[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160314035424.GA7131@jeremy-HP>
Date: Sun, 13 Mar 2016 20:54:24 -0700
From: Jeremy Allison <jra@...ba.org>
To: Andreas Gruenbacher <agruenba@...hat.com>
Cc: Steve French <smfrench@...il.com>,
Christoph Hellwig <hch@...radead.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
"J. Bruce Fields" <bfields@...ldses.org>,
Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
Theodore Ts'o <tytso@....edu>,
"linux-cifs@...r.kernel.org" <linux-cifs@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
Trond Myklebust <trond.myklebust@...marydata.com>,
LKML <linux-kernel@...r.kernel.org>,
XFS Developers <xfs@....sgi.com>,
Andreas Dilger <adilger.kernel@...ger.ca>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Jeff Layton <jlayton@...chiereds.net>,
linux-ext4 <linux-ext4@...r.kernel.org>,
Anna Schumaker <anna.schumaker@...app.com>
Subject: Re: [PATCH v18 00/22] Richacls (Core and Ext4)
On Mon, Mar 14, 2016 at 12:02:13AM +0100, Andreas Gruenbacher wrote:
> On Sat, Mar 12, 2016 at 12:02 AM, Jeremy Allison <jra@...ba.org> wrote:
> > On Fri, Mar 11, 2016 at 02:05:16PM -0600, Steve French wrote:
> >> Sounds like I need to quickly rework the SMB3 ACL helper functions
> >> for cifs.ko
> >>
> >> Also do you know where is the current version of the corresponding
> >> vfs_richacl for
> >> Samba which works with the current RichACL format?
> >
> > I have a patch for a new vfs_richacl somewhere. I remember
> > sending it to Andreas for testing...
>
> Ah, the patch was for testing, not resting ... how could I get that mixed up.
:-).
> I've applied your patch to the latest master branch, made it compile
> again, and fixed a few obvious problems. The results I get with
> smbcacls look reasonable now.
>
> The code is here:
> https://github.com/andreas-gruenbacher/samba richacl
>
> I've used the following smb.conf:
> [richacl]
> comment = Richacl directory
> path = /mnt/ext4
> vfs objects = richacl
> writeable = yes
> browseable = yes
Great ! Once richacls gets into the kernel I'll submit
this into the Samba master branch.
> Is there a particular reason why you didn't make vfs_richacl a
> dynamically loadable module?
Probably sheer lazyness :-).
Powered by blists - more mailing lists