Re: [nfsv4] xattr model in draft-naik-nfsv4-xattrs-01?

[Manoj Naik <[e-mail]>]

"J. Bruce Fields" <[e-mail]> wrote on 10/06/2014 02:23:25 PM:

> From: "J. Bruce Fields" <[e-mail]>
> To: Manoj Naik/Almaden/IBM@IBMUS
> Cc: Christoph Hellwig <[e-mail]>, [e-mail]
> Date: 10/06/2014 02:23 PM
> Subject: Re: [nfsv4] xattr model in draft-naik-nfsv4-xattrs-01?
>
> On Mon, Oct 06, 2014 at 01:59:49PM -0700, Manoj Naik wrote:
> > An operation that replaces ALL the xattr keys of a file with another
set of
> > keys could be done in a compound if we added a separate REMOVEXATTR
that
> > allowed deleting all the xattrs of a file. Otherwise this would need a
> > LISTXATTR, delete individual xattrs and SETXATTR each one, and this
cannot
> > be achieved in a single COMPOUND.
>
> A separate REMOVEXATTR would also make it easier to make it optional.  A
> server could just not implement the one operation.
>
> And easier to remove from the draft when we eventually realize nobody
> cares about it, hah.

I am not sure if you meant to say that in jest, but I would think a server
that implements SETXATTR would implement REMOVEXATTR as well. The latter
would be the only way to delete xattrs, if we decide to separate it from
the current SETXATTR.

Manoj.

>
> --b.
>