Hi Chris & Trond,
On Wed, 2014-06-18 at 15:00 +0200, Christoph Hellwig wrote:
> On Wed, Jun 18, 2014 at 07:35:27AM -0400, Trond Myklebust wrote:
> > Hi Christoph,
> >
> > On Wed, Jun 18, 2014 at 5:07 AM, Christoph Hellwig <hch@xxxxxx> wrote:
> > > The big ACL switched nfs to use generic_listxattr, which calls all existing
> > > ->list handlers. Add a custom .listxattr implementation that only lists
> > > the ACLs if they actually are present on the given inode.
> > >
> > > Signed-off-by: Christoph Hellwig <hch@xxxxxx>
> > > Reported-by: Philippe Troin <phil@xxxxxxxx>
> > > Tested-by: Philippe Troin <phil@xxxxxxxx>
> > > ---
> > > fs/nfs/nfs3acl.c | 43 +++++++++++++++++++++++++++++++++++++++++++
> > > fs/nfs/nfs3proc.c | 4 ++--
> > > 2 files changed, 45 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/fs/nfs/nfs3acl.c b/fs/nfs/nfs3acl.c
> > > index 871d6ed..8f854dd 100644
> > > --- a/fs/nfs/nfs3acl.c
> > > +++ b/fs/nfs/nfs3acl.c
> > > @@ -247,3 +247,46 @@ const struct xattr_handler *nfs3_xattr_handlers[] = {
> > > &posix_acl_default_xattr_handler,
> > > NULL,
> > > };
> > > +
> > > +static int
> > > +nfs3_list_one_acl(struct inode *inode, int type, const char *name, void *data,
> > > + size_t size, ssize_t *result)
> >
> > Why do you make 'result' a pointer to ssize_t rather than a size_t here?
>
> Because ->listxattr returns a ssize_t, and it points to the variable used
> as return value of nfs3_listxattr.
Have these two patches been merged or at least been queued for inclusion
into mainline?
I have just checked 3.15.3, and the patches do not seem to be included
there. I haven't tested that specific kernel revision yet though.
Phil.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
