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;
Date:   Wed, 17 Jun 2020 09:28:14 -0400
To:     Trishali Nayar <ntrishal@in.ibm.com>
Cc:     linux-nfs@vger.kernel.org
Subject: Re: ACL's on 4.1
Message-ID: <20200617132814.GA13815@fieldses.org>
References: <OF7A07A04B.B2FBC2B0-ON00258589.004D5BD3-65258589.004D7269@notes.na.collabserv.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OF7A07A04B.B2FBC2B0-ON00258589.004D5BD3-65258589.004D7269@notes.na.collabserv.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
From:   bfields@fieldses.org (J. Bruce Fields)
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

On Tue, Jun 16, 2020 at 07:35:55PM +0530, Trishali Nayar wrote:
> Hi all,
> 
> Looking at the 4.1 RFC, there are some additional 'Access_mask' and 
> 'Ace-flag' when compared to 4.0.
>  
> - Access_mask:
> ACE4_WRITE_RETENTION
> ACE4_WRITE_RETENTION_HOLD
> 
> - Ace-flag :
> ACE4_INHERITED_ACE
>  
> But are these supported by 4.1 clients and servers?

These are optional.  Linux knfsd does not support them.  I'm not sure
what if any servers do.  If someone was interested in adding client-side
support, it would probably not be hard to add it to nfs4-acl-tools.

--b.

> If you do 'man 
> nfs4_acl' it does not seem to show these additional ones. So how do we 
> set/get them?
> 
> Also, are there any other differences from an ACL perspective between 4.0 
> and 4.1?
>  
> Your insights will be really useful.
>  
> Thanks and regards,
> Trishali.