Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH v3 12/13] NFSv4.2: hook in the user extended attribute handlers
Date:   Fri, 21 Aug 2020 16:03:38 +0000
From:   Frank van der Linden <fllinden@amazon.com>
To:     Murphy Zhou <jencce.kernel@gmail.com>
CC:     linux-nfs <linux-nfs@vger.kernel.org>,
        Anna Schumaker <anna.schumaker@netapp.com>,
        Trond Myklebust <trond.myklebust@hammerspace.com>
Message-ID: <20200821160338.GA30541@dev-dsk-fllinden-2c-c1893d73.us-west-2.amazon.com>
References: <20200623223904.31643-1-fllinden@amazon.com>
 <20200623223904.31643-13-fllinden@amazon.com>
 <CADJHv_tVZ3KzO_RZ18V=e6QBYEFnX5SbyVU6yhh6yCqYMmvmRQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CADJHv_tVZ3KzO_RZ18V=e6QBYEFnX5SbyVU6yhh6yCqYMmvmRQ@mail.gmail.com>
User-Agent: Mutt/1.11.4 (2019-03-13)
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

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@amazon.com> 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.

- Frank