On Fri, 2020-08-21 at 16:03 +0000, Frank van der Linden wrote:
> On Fri, Aug 21, 2020 at 02:50:59PM +0800, Murphy Zhou wrote:
> > Hi,
> >
> > On Wed, Jun 24, 2020 at 6:51 AM Frank van der Linden
> > <fllinden@xxxxxxxxxx> wrote:
> [...]
> > > static const struct inode_operations nfs4_dir_inode_operations =
> > > {
> > > @@ -10146,10 +10254,21 @@ static const struct xattr_handler
> > > nfs4_xattr_nfs4_acl_handler = {
> > > .set = nfs4_xattr_set_nfs4_acl,
> > > };
> > >
> > > +#ifdef CONFIG_NFS_V4_2
> > > +static const struct xattr_handler nfs4_xattr_nfs4_user_handler =
> > > {
> > > + .prefix = XATTR_USER_PREFIX,
> > > + .get = nfs4_xattr_get_nfs4_user,
> > > + .set = nfs4_xattr_set_nfs4_user,
> > > +};
> > > +#endif
> > > +
> >
> > Any plan to support XATTR_TRUSTED_PREFIX ?
> >
> > Thanks.
>
> This is an implementation of RFC 8276, which explicitly restricts
> itself
> to the "user" namespace.
>
> There is currently no portable way to implement the "trusted"
> namespace
> within the boundaries of the NFS specification(s), so it's not
> supported.
>
Correct. 'trusted' is just another way to implement private protocols.
Those are unacceptable in a shared filesystem environment.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@xxxxxxxxxxxxxxx
